From 991c1b28327a22eb7ac8fe838101ec63cd264b9b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Lorber?= <slorber@users.noreply.github.com>
Date: Fri, 10 Dec 2021 14:13:25 +0100
Subject: [PATCH] chore(v2): prepare v2.0.0-beta.11 release (#6081)

---
 CHANGELOG.md                                  |  16 +-
 admin/new.docusaurus.io/package.json          |   2 +-
 lerna.json                                    |   2 +-
 packages/create-docusaurus/package.json       |   2 +-
 .../templates/classic-typescript/package.json |   8 +-
 .../templates/classic/package.json            |   6 +-
 .../templates/facebook/package.json           |   6 +-
 .../docusaurus-cssnano-preset/package.json    |   2 +-
 packages/docusaurus-mdx-loader/package.json   |   6 +-
 packages/docusaurus-migrate/package.json      |   2 +-
 .../package.json                              |   4 +-
 .../package.json                              |  12 +-
 .../package.json                              |  12 +-
 .../package.json                              |  14 +-
 .../package.json                              |  12 +-
 packages/docusaurus-plugin-debug/package.json |   8 +-
 .../package.json                              |   8 +-
 .../package.json                              |   8 +-
 .../package.json                              |   8 +-
 packages/docusaurus-plugin-pwa/package.json   |  14 +-
 .../docusaurus-plugin-sitemap/package.json    |  12 +-
 .../docusaurus-preset-classic/package.json    |  22 +-
 .../package.json                              |   2 +-
 .../docusaurus-theme-classic/package.json     |  22 +-
 packages/docusaurus-theme-common/package.json |  14 +-
 .../package.json                              |  12 +-
 .../package.json                              |  14 +-
 .../package.json                              |   2 +-
 packages/docusaurus-types/package.json        |   2 +-
 packages/docusaurus-utils-common/package.json |   4 +-
 .../docusaurus-utils-validation/package.json  |   4 +-
 packages/docusaurus-utils/package.json        |   4 +-
 packages/docusaurus/package.json              |  16 +-
 packages/lqip-loader/package.json             |   2 +-
 packages/stylelint-copyright/package.json     |   2 +-
 website/package.json                          |  18 +-
 .../_partials/swizzleWarning.mdx              |   0
 .../api/docusaurus.config.js.md               |  15 +
 .../api}/lifecycle-apis.md                    |   2 +
 .../api/plugins/_category_.yml                |   5 +
 .../api/plugins/overview.md                   |   1 +
 .../api/plugins/plugin-client-redirects.md    |   1 +
 .../api/plugins/plugin-content-blog.md        |   2 +
 .../api/plugins/plugin-content-docs.md        |   4 +-
 .../api/plugins/plugin-content-pages.md       |   1 +
 .../api/plugins/plugin-debug.md               |   1 +
 .../api/plugins/plugin-google-analytics.md    |  94 +++
 .../api/plugins/plugin-google-gtag.md         | 100 +++
 .../api/plugins/plugin-ideal-image.md         |   1 +
 .../api/plugins/plugin-pwa.md                 |   1 +
 .../api/plugins/plugin-sitemap.md             |   1 +
 .../api/themes/_category_.yml                 |   5 +
 .../api/themes/overview.md                    |   1 +
 .../api/themes/theme-classic.md               |   1 +
 .../api/themes/theme-configuration.md         |  10 +-
 .../api/themes/theme-live-codeblock.md        |   1 +
 .../api/themes/theme-search-algolia.md        |   1 +
 .../docusaurus-asset-example-banner.png       | Bin
 .../assets/docusaurus-asset-example.docx      | Bin
 .../assets/docusaurus-asset-example.xyz       | Bin
 .../blog.mdx                                  |   0
 .../browser-support.md                        |   0
 .../cli.md                                    |   0
 .../configuration.md                          |  69 +-
 .../version-2.0.0-beta.11/deployment.mdx      | 726 ++++++++++++++++++
 .../docusaurus-core.md                        |  49 ++
 .../guides/creating-pages.md                  |   0
 .../guides/docs/docs-create-doc.mdx           |   0
 .../guides/docs/docs-introduction.md          |   0
 .../guides/docs/docs-markdown-features.mdx    |   0
 .../guides/docs/docs-multi-instance.mdx       |   0
 .../guides/docs/sidebar.md                    | 121 ++-
 .../guides/docs/versioning.md                 |   0
 .../_markdown-partial-example.mdx             |   0
 .../markdown-features-admonitions.mdx         |   0
 .../markdown-features-assets.mdx              |  17 +-
 .../markdown-features-code-blocks.mdx         |   0
 .../markdown-features-head-metadata.mdx}      |  32 +-
 .../markdown-features-headings.mdx            |   0
 .../markdown-features-inline-toc.mdx          |   0
 .../markdown-features-intro.mdx               |   0
 .../markdown-features-math-equations.mdx      |   0
 .../markdown-features-plugins.mdx             |   0
 .../markdown-features-react.mdx               |  47 ++
 .../markdown-features-tabs.mdx                |   0
 .../i18n/i18n-crowdin.mdx                     |   0
 .../i18n/i18n-git.md                          |   0
 .../i18n/i18n-introduction.md                 |   0
 .../i18n/i18n-tutorial.md                     |   0
 .../installation.md                           |   2 +
 .../introduction.md                           |   0
 .../migration/migration-automated.md          |   0
 .../migration/migration-manual.md             |   0
 .../migration/migration-overview.md           |   0
 .../migration/migration-translated-sites.md   |   0
 .../migration/migration-versioned-sites.md    |   0
 .../playground.mdx                            |   0
 .../presets.md                                |   4 +
 .../search.md                                 |  25 +-
 .../version-2.0.0-beta.11/seo.md              | 121 +++
 .../static-assets.md                          |  48 +-
 .../styling-layout.md                         |   0
 .../typescript-support.md                     |   2 +-
 .../using-plugins.md                          |   4 +-
 .../using-themes.md                           |  40 +-
 .../api/plugins/plugin-google-analytics.md    |  34 -
 .../api/plugins/plugin-google-gtag.md         |  41 -
 .../version-2.0.0-beta.9/deployment.mdx       | 587 --------------
 .../version-2.0.0-beta.11-sidebars.json       | 122 +++
 .../version-2.0.0-beta.9-sidebars.json        | 322 --------
 website/versions.json                         |   2 +-
 website/versionsArchived.json                 |   1 +
 112 files changed, 1764 insertions(+), 1204 deletions(-)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/_partials/swizzleWarning.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/docusaurus.config.js.md (97%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11/api}/lifecycle-apis.md (99%)
 create mode 100644 website/versioned_docs/version-2.0.0-beta.11/api/plugins/_category_.yml
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/overview.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-client-redirects.md (99%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-content-blog.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-content-docs.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-content-pages.md (99%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-debug.md (98%)
 create mode 100644 website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-analytics.md
 create mode 100644 website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-gtag.md
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-ideal-image.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-pwa.md (99%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/plugins/plugin-sitemap.md (97%)
 create mode 100644 website/versioned_docs/version-2.0.0-beta.11/api/themes/_category_.yml
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/themes/overview.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/themes/theme-classic.md (95%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/themes/theme-configuration.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/themes/theme-live-codeblock.md (97%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/api/themes/theme-search-algolia.md (97%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/assets/docusaurus-asset-example-banner.png (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/assets/docusaurus-asset-example.docx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/assets/docusaurus-asset-example.xyz (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/blog.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/browser-support.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/cli.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/configuration.md (72%)
 create mode 100644 website/versioned_docs/version-2.0.0-beta.11/deployment.mdx
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/docusaurus-core.md (92%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/creating-pages.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/docs/docs-create-doc.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/docs/docs-introduction.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/docs/docs-markdown-features.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/docs/docs-multi-instance.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/docs/sidebar.md (82%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/docs/versioning.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/_markdown-partial-example.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-admonitions.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-assets.mdx (75%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-code-blocks.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9/guides/markdown-features/markdown-features-head-metadatas.mdx => version-2.0.0-beta.11/guides/markdown-features/markdown-features-head-metadata.mdx} (55%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-headings.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-inline-toc.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-intro.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-math-equations.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-plugins.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-react.mdx (79%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/guides/markdown-features/markdown-features-tabs.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/i18n/i18n-crowdin.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/i18n/i18n-git.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/i18n/i18n-introduction.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/i18n/i18n-tutorial.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/installation.md (97%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/introduction.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/migration/migration-automated.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/migration/migration-manual.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/migration/migration-overview.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/migration/migration-translated-sites.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/migration/migration-versioned-sites.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/playground.mdx (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/presets.md (94%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/search.md (95%)
 create mode 100644 website/versioned_docs/version-2.0.0-beta.11/seo.md
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/static-assets.md (61%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/styling-layout.md (100%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/typescript-support.md (97%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/using-plugins.md (98%)
 rename website/versioned_docs/{version-2.0.0-beta.9 => version-2.0.0-beta.11}/using-themes.md (74%)
 delete mode 100644 website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-analytics.md
 delete mode 100644 website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-gtag.md
 delete mode 100644 website/versioned_docs/version-2.0.0-beta.9/deployment.mdx
 create mode 100644 website/versioned_sidebars/version-2.0.0-beta.11-sidebars.json
 delete mode 100644 website/versioned_sidebars/version-2.0.0-beta.9-sidebars.json

diff --git a/CHANGELOG.md b/CHANGELOG.md
index bf15bd7513..16ea0cf654 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,17 @@
 # Docusaurus 2 Changelog
 
+## 2.0.0-beta.11 (2021-12-10)
+
+#### :bug: Bug Fix
+
+- `docusaurus-plugin-client-redirects`, `docusaurus-plugin-content-blog`, `docusaurus-plugin-content-docs`, `docusaurus-plugin-content-pages`, `docusaurus-plugin-debug`, `docusaurus-plugin-google-analytics`, `docusaurus-plugin-google-gtag`, `docusaurus-plugin-ideal-image`, `docusaurus-plugin-pwa`, `docusaurus-plugin-sitemap`, `docusaurus-preset-classic`, `docusaurus-theme-classic`, `docusaurus-theme-common`, `docusaurus-theme-live-codeblock`, `docusaurus-theme-search-algolia`
+  - [#6078](https://github.com/facebook/docusaurus/pull/6078) fix: move docusaurus core back to hard dependencies ([@pranabdas](https://github.com/pranabdas))
+
+#### Committers: 2
+
+- Pranab Das ([@pranabdas](https://github.com/pranabdas))
+- Sébastien Lorber ([@slorber](https://github.com/slorber))
+
 ## 2.0.0-beta.10 (2021-12-09)
 
 #### :rocket: New Feature
@@ -2169,7 +2181,7 @@ Starting with this release for a proper work of i18n functionality, you need to
 - [@wolf20482](https://github.com/wolf20482)
 - moonrailgun ([@moonrailgun](https://github.com/moonrailgun))
 - Çağlar Turalı ([@caglarturali](https://github.com/caglarturali))
-- 琚致远 ([@juzhiyuan](https://github.com/juzhiyuan)) ✨ Done in 15.23s.
+- 琚致远 ([@juzhiyuan](https://github.com/juzhiyuan))
 
 ## 2.0.0-alpha.70 (2020-12-17)
 
@@ -3033,7 +3045,7 @@ Failed release
 - Méril ([@mpsq](https://github.com/mpsq))
 - Sébastien Lorber ([@slorber](https://github.com/slorber))
 - Teik Jun ([@teikjun](https://github.com/teikjun))
-- Xuqian ([@zxuqian](https://github.com/zxuqian)) ✨ Done in 3.58s.
+- Xuqian ([@zxuqian](https://github.com/zxuqian))
 
 ## 2.0.0-alpha.60 (2020-07-29)
 
diff --git a/admin/new.docusaurus.io/package.json b/admin/new.docusaurus.io/package.json
index ffc0291543..38c2ce9451 100644
--- a/admin/new.docusaurus.io/package.json
+++ b/admin/new.docusaurus.io/package.json
@@ -1,6 +1,6 @@
 {
   "name": "new.docusaurus.io",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "private": true,
   "scripts": {
     "start": "netlify dev"
diff --git a/lerna.json b/lerna.json
index 8f9bc2ae1e..bd1fa035f2 100644
--- a/lerna.json
+++ b/lerna.json
@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "npmClient": "yarn",
   "useWorkspaces": true,
   "changelog": {
diff --git a/packages/create-docusaurus/package.json b/packages/create-docusaurus/package.json
index 665dae8504..97787e094f 100755
--- a/packages/create-docusaurus/package.json
+++ b/packages/create-docusaurus/package.json
@@ -1,6 +1,6 @@
 {
   "name": "create-docusaurus",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Create Docusaurus apps easily.",
   "repository": {
     "type": "git",
diff --git a/packages/create-docusaurus/templates/classic-typescript/package.json b/packages/create-docusaurus/templates/classic-typescript/package.json
index efe669805b..e729f697f6 100644
--- a/packages/create-docusaurus/templates/classic-typescript/package.json
+++ b/packages/create-docusaurus/templates/classic-typescript/package.json
@@ -1,6 +1,6 @@
 {
   "name": "docusaurus-2-classic-typescript-template",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",
@@ -15,8 +15,8 @@
     "typecheck": "tsc"
   },
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/preset-classic": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/preset-classic": "2.0.0-beta.11",
     "@mdx-js/react": "^1.6.21",
     "clsx": "^1.1.1",
     "prism-react-renderer": "^1.2.1",
@@ -24,7 +24,7 @@
     "react-dom": "^17.0.1"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
     "@tsconfig/docusaurus": "^1.0.4",
     "typescript": "^4.5.2"
   },
diff --git a/packages/create-docusaurus/templates/classic/package.json b/packages/create-docusaurus/templates/classic/package.json
index b0f9d92f54..9b5e42cf68 100644
--- a/packages/create-docusaurus/templates/classic/package.json
+++ b/packages/create-docusaurus/templates/classic/package.json
@@ -1,6 +1,6 @@
 {
   "name": "docusaurus-2-classic-template",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",
@@ -14,8 +14,8 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/preset-classic": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/preset-classic": "2.0.0-beta.11",
     "@mdx-js/react": "^1.6.21",
     "clsx": "^1.1.1",
     "prism-react-renderer": "^1.2.1",
diff --git a/packages/create-docusaurus/templates/facebook/package.json b/packages/create-docusaurus/templates/facebook/package.json
index 750baf9ddc..3bb492c18d 100644
--- a/packages/create-docusaurus/templates/facebook/package.json
+++ b/packages/create-docusaurus/templates/facebook/package.json
@@ -1,6 +1,6 @@
 {
   "name": "docusaurus-2-facebook-template",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",
@@ -18,8 +18,8 @@
     "format:diff": "prettier --config .prettierrc --list-different \"**/*.{js,jsx,ts,tsx,md,mdx}\""
   },
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/preset-classic": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/preset-classic": "2.0.0-beta.11",
     "@mdx-js/react": "^1.6.21",
     "clsx": "^1.1.1",
     "react": "^17.0.1",
diff --git a/packages/docusaurus-cssnano-preset/package.json b/packages/docusaurus-cssnano-preset/package.json
index f44612a556..768e8fd832 100644
--- a/packages/docusaurus-cssnano-preset/package.json
+++ b/packages/docusaurus-cssnano-preset/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/cssnano-preset",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Advanced cssnano preset for maximum optimization.",
   "main": "index.js",
   "license": "MIT",
diff --git a/packages/docusaurus-mdx-loader/package.json b/packages/docusaurus-mdx-loader/package.json
index 4047a9914d..b2bd549d4d 100644
--- a/packages/docusaurus-mdx-loader/package.json
+++ b/packages/docusaurus-mdx-loader/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/mdx-loader",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docusaurus Loader for MDX",
   "main": "lib/index.js",
   "types": "src/mdx-loader.d.ts",
@@ -20,7 +20,7 @@
   "dependencies": {
     "@babel/parser": "^7.16.4",
     "@babel/traverse": "^7.16.3",
-    "@docusaurus/utils": "2.0.0-beta.10",
+    "@docusaurus/utils": "2.0.0-beta.11",
     "@mdx-js/mdx": "^1.6.21",
     "@mdx-js/react": "^1.6.21",
     "chalk": "^4.1.2",
@@ -37,7 +37,7 @@
     "webpack": "^5.61.0"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/escape-html": "^1.0.1",
     "@types/mdast": "^3.0.7",
     "@types/stringify-object": "^3.3.1",
diff --git a/packages/docusaurus-migrate/package.json b/packages/docusaurus-migrate/package.json
index a3443e170c..97fb512687 100644
--- a/packages/docusaurus-migrate/package.json
+++ b/packages/docusaurus-migrate/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/migrate",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "A CLI tool to migrate from older versions of Docusaurus.",
   "main": "lib/index.js",
   "license": "MIT",
diff --git a/packages/docusaurus-module-type-aliases/package.json b/packages/docusaurus-module-type-aliases/package.json
index 9c7ee6d131..34b69cc922 100644
--- a/packages/docusaurus-module-type-aliases/package.json
+++ b/packages/docusaurus-module-type-aliases/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/module-type-aliases",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docusaurus module type aliases.",
   "types": "./src/index.d.ts",
   "publishConfig": {
@@ -12,7 +12,7 @@
     "directory": "packages/docusaurus-module-type-aliases"
   },
   "dependencies": {
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/react": "*",
     "@types/react-helmet": "*",
     "@types/react-router-config": "*",
diff --git a/packages/docusaurus-plugin-client-redirects/package.json b/packages/docusaurus-plugin-client-redirects/package.json
index 5f368cf6ed..db9ae936e5 100644
--- a/packages/docusaurus-plugin-client-redirects/package.json
+++ b/packages/docusaurus-plugin-client-redirects/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-client-redirects",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Client redirects plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-client-redirects.d.ts",
@@ -18,10 +18,10 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-common": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-common": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "chalk": "^4.1.2",
     "eta": "^1.12.3",
     "fs-extra": "^10.0.0",
@@ -29,7 +29,7 @@
     "tslib": "^2.3.1"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-plugin-content-blog/package.json b/packages/docusaurus-plugin-content-blog/package.json
index e800edc501..6d891a5a70 100644
--- a/packages/docusaurus-plugin-content-blog/package.json
+++ b/packages/docusaurus-plugin-content-blog/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-content-blog",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Blog plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-content-blog.d.ts",
@@ -18,10 +18,10 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/mdx-loader": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/mdx-loader": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "chalk": "^4.1.2",
     "escape-string-regexp": "^4.0.0",
     "feed": "^4.2.2",
@@ -37,7 +37,7 @@
     "webpack": "^5.61.0"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-plugin-content-docs/package.json b/packages/docusaurus-plugin-content-docs/package.json
index dbd0ef53ae..8e9bcb5a0f 100644
--- a/packages/docusaurus-plugin-content-docs/package.json
+++ b/packages/docusaurus-plugin-content-docs/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-content-docs",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docs plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-content-docs.d.ts",
@@ -18,10 +18,10 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/mdx-loader": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/mdx-loader": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "chalk": "^4.1.2",
     "combine-promises": "^1.1.0",
     "escape-string-regexp": "^4.0.0",
@@ -38,8 +38,8 @@
     "webpack": "^5.61.0"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/js-yaml": "^4.0.0",
     "@types/picomatch": "^2.2.1",
     "commander": "^5.1.0",
diff --git a/packages/docusaurus-plugin-content-pages/package.json b/packages/docusaurus-plugin-content-pages/package.json
index bbae9b6ce7..5b72945510 100644
--- a/packages/docusaurus-plugin-content-pages/package.json
+++ b/packages/docusaurus-plugin-content-pages/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-content-pages",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Pages plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-content-pages.d.ts",
@@ -18,17 +18,17 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/mdx-loader": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/mdx-loader": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "globby": "^11.0.2",
     "remark-admonitions": "^1.2.1",
     "tslib": "^2.3.1",
     "webpack": "^5.61.0"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-plugin-debug/package.json b/packages/docusaurus-plugin-debug/package.json
index 149c4af05e..df50078b83 100644
--- a/packages/docusaurus-plugin-debug/package.json
+++ b/packages/docusaurus-plugin-debug/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-debug",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Debug plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-debug.d.ts",
@@ -18,14 +18,14 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
     "fs-extra": "^10.0.0",
     "react-json-view": "^1.21.3",
     "tslib": "^2.3.1"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-plugin-google-analytics/package.json b/packages/docusaurus-plugin-google-analytics/package.json
index 5d40702495..1a81c56d49 100644
--- a/packages/docusaurus-plugin-google-analytics/package.json
+++ b/packages/docusaurus-plugin-google-analytics/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-google-analytics",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Global analytics (analytics.js) plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-google-analytics.d.ts",
@@ -18,11 +18,11 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10"
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-plugin-google-gtag/package.json b/packages/docusaurus-plugin-google-gtag/package.json
index acd62ace8e..e0d9082346 100644
--- a/packages/docusaurus-plugin-google-gtag/package.json
+++ b/packages/docusaurus-plugin-google-gtag/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-google-gtag",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Global Site Tag (gtag.js) plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-google-gtag.d.ts",
@@ -18,11 +18,11 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10"
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-plugin-ideal-image/package.json b/packages/docusaurus-plugin-ideal-image/package.json
index f1019e743e..5e1f3070ea 100644
--- a/packages/docusaurus-plugin-ideal-image/package.json
+++ b/packages/docusaurus-plugin-ideal-image/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-ideal-image",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docusaurus Plugin to generate an almost ideal image (responsive, lazy-loading, and low quality placeholder).",
   "main": "lib/index.js",
   "types": "src/plugin-ideal-image.d.ts",
@@ -21,8 +21,8 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/lqip-loader": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/lqip-loader": "2.0.0-beta.11",
     "@docusaurus/responsive-loader": "1.5.0",
     "@endiliey/react-ideal-image": "^0.0.11",
     "react-waypoint": "^10.1.0",
@@ -31,7 +31,7 @@
     "webpack": "^5.61.0"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/types": "2.0.0-beta.11",
     "fs-extra": "^10.0.0"
   },
   "peerDependencies": {
diff --git a/packages/docusaurus-plugin-pwa/package.json b/packages/docusaurus-plugin-pwa/package.json
index f6d8546437..eb049331bb 100644
--- a/packages/docusaurus-plugin-pwa/package.json
+++ b/packages/docusaurus-plugin-pwa/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-pwa",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docusaurus Plugin to add PWA support.",
   "main": "lib/index.js",
   "types": "src/plugin-pwa.d.ts",
@@ -23,11 +23,11 @@
     "@babel/plugin-proposal-nullish-coalescing-operator": "^7.16.0",
     "@babel/plugin-proposal-optional-chaining": "^7.16.0",
     "@babel/preset-env": "^7.16.4",
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/theme-common": "2.0.0-beta.10",
-    "@docusaurus/theme-translations": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/theme-common": "2.0.0-beta.11",
+    "@docusaurus/theme-translations": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "babel-loader": "^8.2.2",
     "clsx": "^1.1.1",
     "core-js": "^3.18.0",
@@ -39,7 +39,7 @@
     "workbox-window": "^6.1.1"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
     "fs-extra": "^10.0.0"
   },
   "peerDependencies": {
diff --git a/packages/docusaurus-plugin-sitemap/package.json b/packages/docusaurus-plugin-sitemap/package.json
index 2698b844fb..1717c3ad6b 100644
--- a/packages/docusaurus-plugin-sitemap/package.json
+++ b/packages/docusaurus-plugin-sitemap/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/plugin-sitemap",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Simple sitemap generation plugin for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/plugin-sitemap.d.ts",
@@ -18,16 +18,16 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-common": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-common": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "fs-extra": "^10.0.0",
     "sitemap": "^7.0.0",
     "tslib": "^2.3.1"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-preset-classic/package.json b/packages/docusaurus-preset-classic/package.json
index 29953a7acf..fefdf4bb60 100644
--- a/packages/docusaurus-preset-classic/package.json
+++ b/packages/docusaurus-preset-classic/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/preset-classic",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Classic preset for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/preset-classic.d.ts",
@@ -18,16 +18,16 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-blog": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-docs": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-pages": "2.0.0-beta.10",
-    "@docusaurus/plugin-debug": "2.0.0-beta.10",
-    "@docusaurus/plugin-google-analytics": "2.0.0-beta.10",
-    "@docusaurus/plugin-google-gtag": "2.0.0-beta.10",
-    "@docusaurus/plugin-sitemap": "2.0.0-beta.10",
-    "@docusaurus/theme-classic": "2.0.0-beta.10",
-    "@docusaurus/theme-search-algolia": "2.0.0-beta.10"
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-blog": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-docs": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-pages": "2.0.0-beta.11",
+    "@docusaurus/plugin-debug": "2.0.0-beta.11",
+    "@docusaurus/plugin-google-analytics": "2.0.0-beta.11",
+    "@docusaurus/plugin-google-gtag": "2.0.0-beta.11",
+    "@docusaurus/plugin-sitemap": "2.0.0-beta.11",
+    "@docusaurus/theme-classic": "2.0.0-beta.11",
+    "@docusaurus/theme-search-algolia": "2.0.0-beta.11"
   },
   "peerDependencies": {
     "react": "^16.8.4 || ^17.0.0",
diff --git a/packages/docusaurus-remark-plugin-npm2yarn/package.json b/packages/docusaurus-remark-plugin-npm2yarn/package.json
index e6c0e1e5a8..5131071a5d 100644
--- a/packages/docusaurus-remark-plugin-npm2yarn/package.json
+++ b/packages/docusaurus-remark-plugin-npm2yarn/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/remark-plugin-npm2yarn",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Remark plugin for converting npm commands to Yarn commands as tabs.",
   "main": "lib/index.js",
   "publishConfig": {
diff --git a/packages/docusaurus-theme-classic/package.json b/packages/docusaurus-theme-classic/package.json
index 30c6d90dfb..7db7e8a9f2 100644
--- a/packages/docusaurus-theme-classic/package.json
+++ b/packages/docusaurus-theme-classic/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/theme-classic",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Classic theme for Docusaurus",
   "main": "lib/index.js",
   "types": "src/theme-classic.d.ts",
@@ -23,13 +23,13 @@
     "update-code-translations": "node -e 'require(\"./update-code-translations.js\").run()'"
   },
   "dependencies": {
-    "@docusaurus/plugin-content-blog": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-docs": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-pages": "2.0.0-beta.10",
-    "@docusaurus/theme-common": "2.0.0-beta.10",
-    "@docusaurus/theme-translations": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/plugin-content-blog": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-docs": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-pages": "2.0.0-beta.11",
+    "@docusaurus/theme-common": "2.0.0-beta.11",
+    "@docusaurus/theme-translations": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "@mdx-js/mdx": "^1.6.21",
     "@mdx-js/react": "^1.6.21",
     "chalk": "^4.1.2",
@@ -45,9 +45,9 @@
     "rtlcss": "^3.3.0"
   },
   "devDependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/mdx-js__react": "^1.5.4",
     "@types/parse-numeric-range": "^0.0.1",
     "@types/rtlcss": "^3.1.1",
diff --git a/packages/docusaurus-theme-common/package.json b/packages/docusaurus-theme-common/package.json
index a3f3fd742c..67d008a031 100644
--- a/packages/docusaurus-theme-common/package.json
+++ b/packages/docusaurus-theme-common/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/theme-common",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Common code for Docusaurus themes.",
   "main": "./lib/index.js",
   "types": "./lib/index.d.ts",
@@ -18,9 +18,9 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/plugin-content-blog": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-docs": "2.0.0-beta.10",
-    "@docusaurus/plugin-content-pages": "2.0.0-beta.10",
+    "@docusaurus/plugin-content-blog": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-docs": "2.0.0-beta.11",
+    "@docusaurus/plugin-content-pages": "2.0.0-beta.11",
     "clsx": "^1.1.1",
     "fs-extra": "^10.0.0",
     "parse-numeric-range": "^1.3.0",
@@ -28,9 +28,9 @@
     "utility-types": "^3.10.0"
   },
   "devDependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@testing-library/react-hooks": "^7.0.2",
     "lodash": "^4.17.20"
   },
diff --git a/packages/docusaurus-theme-live-codeblock/package.json b/packages/docusaurus-theme-live-codeblock/package.json
index 8c44589b3f..6a44eb1f79 100644
--- a/packages/docusaurus-theme-live-codeblock/package.json
+++ b/packages/docusaurus-theme-live-codeblock/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/theme-live-codeblock",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docusaurus live code block component.",
   "main": "lib/index.js",
   "publishConfig": {
@@ -17,10 +17,10 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/theme-translations": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/theme-translations": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "@philpl/buble": "^0.19.7",
     "clsx": "^1.1.1",
     "fs-extra": "^10.0.0",
@@ -29,7 +29,7 @@
     "react-live": "2.2.3"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/buble": "^0.20.1"
   },
   "peerDependencies": {
diff --git a/packages/docusaurus-theme-search-algolia/package.json b/packages/docusaurus-theme-search-algolia/package.json
index ac4da1a7cf..993fa10261 100644
--- a/packages/docusaurus-theme-search-algolia/package.json
+++ b/packages/docusaurus-theme-search-algolia/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/theme-search-algolia",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Algolia search component for Docusaurus.",
   "main": "lib/index.js",
   "types": "src/theme-search-algolia.d.ts",
@@ -21,11 +21,11 @@
   },
   "dependencies": {
     "@docsearch/react": "^3.0.0-alpha.39",
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/theme-common": "2.0.0-beta.10",
-    "@docusaurus/theme-translations": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/theme-common": "2.0.0-beta.11",
+    "@docusaurus/theme-translations": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "algoliasearch": "^4.10.5",
     "algoliasearch-helper": "^3.5.5",
     "clsx": "^1.1.1",
@@ -33,7 +33,7 @@
     "lodash": "^4.17.20"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
     "fs-extra": "^10.0.0"
   },
   "peerDependencies": {
diff --git a/packages/docusaurus-theme-translations/package.json b/packages/docusaurus-theme-translations/package.json
index 37604200f3..8b96c88695 100644
--- a/packages/docusaurus-theme-translations/package.json
+++ b/packages/docusaurus-theme-translations/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/theme-translations",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Docusaurus theme translations.",
   "main": "lib/index.js",
   "types": "lib/index.d.ts",
diff --git a/packages/docusaurus-types/package.json b/packages/docusaurus-types/package.json
index f5d9fd9fc7..954e1ae0dd 100644
--- a/packages/docusaurus-types/package.json
+++ b/packages/docusaurus-types/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/types",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Common types for Docusaurus packages.",
   "types": "./src/index.d.ts",
   "publishConfig": {
diff --git a/packages/docusaurus-utils-common/package.json b/packages/docusaurus-utils-common/package.json
index f1576488de..cc16ed83c6 100644
--- a/packages/docusaurus-utils-common/package.json
+++ b/packages/docusaurus-utils-common/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/utils-common",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Common (Node/Browser) utility functions for Docusaurus packages.",
   "main": "./lib/index.js",
   "types": "./lib/index.d.ts",
@@ -21,7 +21,7 @@
     "tslib": "^2.3.1"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10"
+    "@docusaurus/types": "2.0.0-beta.11"
   },
   "engines": {
     "node": ">=14"
diff --git a/packages/docusaurus-utils-validation/package.json b/packages/docusaurus-utils-validation/package.json
index 5ad42258a0..2fd8af9eef 100644
--- a/packages/docusaurus-utils-validation/package.json
+++ b/packages/docusaurus-utils-validation/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/utils-validation",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Node validation utility functions for Docusaurus packages.",
   "main": "./lib/index.js",
   "types": "./lib/index.d.ts",
@@ -18,7 +18,7 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@docusaurus/utils": "2.0.0-beta.10",
+    "@docusaurus/utils": "2.0.0-beta.11",
     "chalk": "^4.1.2",
     "joi": "^17.4.2",
     "tslib": "^2.3.1"
diff --git a/packages/docusaurus-utils/package.json b/packages/docusaurus-utils/package.json
index c66f90e58b..245b98c4d6 100644
--- a/packages/docusaurus-utils/package.json
+++ b/packages/docusaurus-utils/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/utils",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Node utility functions for Docusaurus packages.",
   "main": "./lib/index.js",
   "types": "./lib/index.d.ts",
@@ -39,7 +39,7 @@
     "node": ">=14"
   },
   "devDependencies": {
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/dedent": "^0.7.0",
     "@types/github-slugger": "^1.3.0",
     "@types/micromatch": "^4.0.2",
diff --git a/packages/docusaurus/package.json b/packages/docusaurus/package.json
index 1927424ca2..d70ec57f27 100644
--- a/packages/docusaurus/package.json
+++ b/packages/docusaurus/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@docusaurus/core",
   "description": "Easy to Maintain Open Source Documentation Websites",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "license": "MIT",
   "publishConfig": {
     "access": "public"
@@ -41,12 +41,12 @@
     "@babel/runtime": "^7.16.3",
     "@babel/runtime-corejs3": "^7.16.3",
     "@babel/traverse": "^7.16.3",
-    "@docusaurus/cssnano-preset": "2.0.0-beta.10",
-    "@docusaurus/mdx-loader": "2.0.0-beta.10",
+    "@docusaurus/cssnano-preset": "2.0.0-beta.11",
+    "@docusaurus/mdx-loader": "2.0.0-beta.11",
     "@docusaurus/react-loadable": "5.5.2",
-    "@docusaurus/utils": "2.0.0-beta.10",
-    "@docusaurus/utils-common": "2.0.0-beta.10",
-    "@docusaurus/utils-validation": "2.0.0-beta.10",
+    "@docusaurus/utils": "2.0.0-beta.11",
+    "@docusaurus/utils-common": "2.0.0-beta.11",
+    "@docusaurus/utils-validation": "2.0.0-beta.11",
     "@slorber/static-site-generator-webpack-plugin": "^4.0.0",
     "@svgr/webpack": "^6.0.0",
     "autoprefixer": "^10.3.5",
@@ -108,8 +108,8 @@
     "webpackbar": "^5.0.0-3"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "2.0.0-beta.10",
-    "@docusaurus/types": "2.0.0-beta.10",
+    "@docusaurus/module-type-aliases": "2.0.0-beta.11",
+    "@docusaurus/types": "2.0.0-beta.11",
     "@types/copy-webpack-plugin": "^8.0.1",
     "@types/css-minimizer-webpack-plugin": "^3.0.2",
     "@types/detect-port": "^1.3.0",
diff --git a/packages/lqip-loader/package.json b/packages/lqip-loader/package.json
index 6513944e5b..e721161f46 100644
--- a/packages/lqip-loader/package.json
+++ b/packages/lqip-loader/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@docusaurus/lqip-loader",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Low Quality Image Placeholders (LQIP) loader for webpack.",
   "main": "lib/index.js",
   "publishConfig": {
diff --git a/packages/stylelint-copyright/package.json b/packages/stylelint-copyright/package.json
index a38c098fe9..d2529a9914 100644
--- a/packages/stylelint-copyright/package.json
+++ b/packages/stylelint-copyright/package.json
@@ -1,6 +1,6 @@
 {
   "name": "stylelint-copyright",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Stylelint plugin to check CSS files for a copyright header.",
   "main": "index.js",
   "license": "MIT",
diff --git a/website/package.json b/website/package.json
index e3e0827eee..8734d3e661 100644
--- a/website/package.json
+++ b/website/package.json
@@ -1,6 +1,6 @@
 {
   "name": "website",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",
@@ -31,14 +31,14 @@
   "dependencies": {
     "@crowdin/cli": "^3.7.1",
     "@crowdin/crowdin-api-client": "^1.10.6",
-    "@docusaurus/core": "2.0.0-beta.10",
-    "@docusaurus/plugin-client-redirects": "2.0.0-beta.10",
-    "@docusaurus/plugin-ideal-image": "2.0.0-beta.10",
-    "@docusaurus/plugin-pwa": "2.0.0-beta.10",
-    "@docusaurus/preset-classic": "2.0.0-beta.10",
-    "@docusaurus/remark-plugin-npm2yarn": "2.0.0-beta.10",
-    "@docusaurus/theme-live-codeblock": "2.0.0-beta.10",
-    "@docusaurus/utils": "2.0.0-beta.10",
+    "@docusaurus/core": "2.0.0-beta.11",
+    "@docusaurus/plugin-client-redirects": "2.0.0-beta.11",
+    "@docusaurus/plugin-ideal-image": "2.0.0-beta.11",
+    "@docusaurus/plugin-pwa": "2.0.0-beta.11",
+    "@docusaurus/preset-classic": "2.0.0-beta.11",
+    "@docusaurus/remark-plugin-npm2yarn": "2.0.0-beta.11",
+    "@docusaurus/theme-live-codeblock": "2.0.0-beta.11",
+    "@docusaurus/utils": "2.0.0-beta.11",
     "@popperjs/core": "^2.10.2",
     "clsx": "^1.1.1",
     "color": "^4.0.1",
diff --git a/website/versioned_docs/version-2.0.0-beta.9/_partials/swizzleWarning.mdx b/website/versioned_docs/version-2.0.0-beta.11/_partials/swizzleWarning.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/_partials/swizzleWarning.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/_partials/swizzleWarning.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/docusaurus.config.js.md b/website/versioned_docs/version-2.0.0-beta.11/api/docusaurus.config.js.md
similarity index 97%
rename from website/versioned_docs/version-2.0.0-beta.9/api/docusaurus.config.js.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/docusaurus.config.js.md
index 92fe87b4e7..3365619a44 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/docusaurus.config.js.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/docusaurus.config.js.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 0
 id: docusaurus.config.js
 description: API reference for Docusaurus configuration file.
 slug: /api/docusaurus-config
@@ -360,6 +361,20 @@ Attempting to add unknown field in the config will lead to error in build time:
 Error: The field(s) 'foo', 'bar' are not recognized in docusaurus.config.js
 ```
 
+### `staticDirectories` {#staticdirectories}
+
+An array of paths, relative to the site's directory or absolute. Files under these paths will be copied to the build output as-is.
+
+- Type: `string[]`
+
+Example:
+
+```js title="docusaurus.config.js"
+module.exports = {
+  staticDirectories: ['static'],
+};
+```
+
 ### `scripts` {#scripts}
 
 An array of scripts to load. The values can be either strings or plain objects of attribute-value maps. The `<script>` tags will be inserted in the HTML `<head>`.
diff --git a/website/versioned_docs/version-2.0.0-beta.9/lifecycle-apis.md b/website/versioned_docs/version-2.0.0-beta.11/api/lifecycle-apis.md
similarity index 99%
rename from website/versioned_docs/version-2.0.0-beta.9/lifecycle-apis.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/lifecycle-apis.md
index 8dd9d25772..9f6aeab8e3 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/lifecycle-apis.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/lifecycle-apis.md
@@ -1,6 +1,8 @@
 ---
+sidebar_position: 1
 id: lifecycle-apis
 title: Lifecycle APIs
+slug: /lifecycle-apis
 toc_max_heading_level: 4
 ---
 
diff --git a/website/versioned_docs/version-2.0.0-beta.11/api/plugins/_category_.yml b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/_category_.yml
new file mode 100644
index 0000000000..cffabddbd5
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/_category_.yml
@@ -0,0 +1,5 @@
+label: Plugins
+position: 2
+link:
+  type: doc
+  id: api/plugins/plugins-overview # Dogfood using a "qualified id"
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/overview.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/overview.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/overview.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/overview.md
index bbacce0047..31897e73e6 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/overview.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/overview.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 0
 id: plugins-overview
 title: 'Docusaurus plugins'
 sidebar_label: Plugins overview
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-client-redirects.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-client-redirects.md
similarity index 99%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-client-redirects.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-client-redirects.md
index 722662c903..fca62c4555 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-client-redirects.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-client-redirects.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 4
 id: plugin-client-redirects
 title: '📦 plugin-client-redirects'
 slug: '/api/plugins/@docusaurus/plugin-client-redirects'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-blog.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-blog.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-blog.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-blog.md
index c54bd3164c..06d7bdca5b 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-blog.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-blog.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 2
 id: plugin-content-blog
 title: '📦 plugin-content-blog'
 slug: '/api/plugins/@docusaurus/plugin-content-blog'
@@ -61,6 +62,7 @@ Accepted fields:
 | `feedOptions.description` | `string` | <code>\`${siteConfig.title} Blog\`</code> | Description of the feed. |
 | `feedOptions.copyright` | `string` | `undefined` | Copyright message. |
 | `feedOptions.language` | `string` (See [documentation](http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes) for possible values) | `undefined` | Language metadata of the feed. |
+| `sortPosts` | <code>'descending' \| 'ascending' </code> | `'descending'` | Governs the direction of blog post sorting. |
 
 </APITable>
 
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-docs.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-docs.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-docs.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-docs.md
index 3b92343ab5..0be06dc360 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-docs.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-docs.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 1
 id: plugin-content-docs
 title: '📦 plugin-content-docs'
 slug: '/api/plugins/@docusaurus/plugin-content-docs'
@@ -47,6 +48,7 @@ Accepted fields:
 | `docItemComponent` | `string` | `'@theme/DocItem'` | Main doc container, with TOC, pagination, etc. |
 | `docTagsListComponent` | `string` | `'@theme/DocTagsListPage'` | Root component of the tags list page |
 | `docTagDocListComponent` | `string` | `'@theme/DocTagDocListPage'` | Root component of the "docs containing tag" page. |
+| `docCategoryGeneratedIndexComponent` | `string` | `'@theme/DocCategoryGeneratedIndexPage'` | Root component of the generated category index page. |
 | `remarkPlugins` | `any[]` | `[]` | Remark plugins passed to MDX. |
 | `rehypePlugins` | `any[]` | `[]` | Rehype plugins passed to MDX. |
 | `beforeDefaultRemarkPlugins` | `any[]` | `[]` | Custom Remark plugins passed to MDX before the default Docusaurus Remark plugins. |
@@ -248,7 +250,7 @@ Accepted fields:
 | `title` | `string` | Markdown title or `id` | The text title of your document. Used for the page metadata and as a fallback value in multiple places (sidebar, next/previous buttons...). Automatically added at the top of your doc if it does not contain any Markdown title. |
 | `pagination_label` | `string` | `sidebar_label` or `title` | The text used in the document next/previous buttons for this document. |
 | `sidebar_label` | `string` | `title` | The text shown in the document sidebar for this document. |
-| `sidebar_position` | `number` | Default ordering | Controls the position of a doc inside the generated sidebar slice when using `autogenerated` sidebar items. See also [Autogenerated sidebar metadatas](/docs/sidebar#autogenerated-sidebar-metadatas). |
+| `sidebar_position` | `number` | Default ordering | Controls the position of a doc inside the generated sidebar slice when using `autogenerated` sidebar items. See also [Autogenerated sidebar metadata](/docs/sidebar#autogenerated-sidebar-metadata). |
 | `sidebar_class_name` | `string` | `undefined` | Gives the corresponding sidebar label a special class name when using autogenerated sidebars. |
 | `hide_title` | `boolean` | `false` | Whether to hide the title at the top of the doc. It only hides a title declared through the frontmatter, and have no effect on a Markdown title at the top of your document. |
 | `hide_table_of_contents` | `boolean` | `false` | Whether to hide the table of contents to the right. |
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-pages.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-pages.md
similarity index 99%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-pages.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-pages.md
index 89e30a8778..971ab7c925 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-content-pages.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-content-pages.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 3
 id: plugin-content-pages
 title: '📦 plugin-content-pages'
 slug: '/api/plugins/@docusaurus/plugin-content-pages'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-debug.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-debug.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-debug.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-debug.md
index c307099525..43f57305b5 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-debug.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-debug.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 5
 id: plugin-debug
 title: '📦 plugin-debug'
 slug: '/api/plugins/@docusaurus/plugin-debug'
diff --git a/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-analytics.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-analytics.md
new file mode 100644
index 0000000000..c38a45394b
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-analytics.md
@@ -0,0 +1,94 @@
+---
+sidebar_position: 6
+id: plugin-google-analytics
+title: '📦 plugin-google-analytics'
+slug: '/api/plugins/@docusaurus/plugin-google-analytics'
+---
+
+The default [Google Analytics](https://developers.google.com/analytics/devguides/collection/analyticsjs/) plugin. It is a JavaScript library for measuring how users interact with your website **in the production build**. If you are using Google Analytics 4 you might need to consider using [plugin-google-gtag](./plugin-google-gtag.md) instead.
+
+## Installation {#installation}
+
+```bash npm2yarn
+npm install --save @docusaurus/plugin-google-analytics
+```
+
+:::tip
+
+If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
+
+:::
+
+## Configuration {#configuration}
+
+Accepted fields:
+
+<small>
+
+| Name | Type | Default | Description |
+| --- | --- | --- | --- |
+| `trackingID` | `string` | **Required** | The tracking ID of your analytics service. |
+| `anonymizeIP` | `boolean` | `false` | Whether the IP should be anonymized when sending requests. |
+
+</small>
+
+## Example configuration {#ex-config}
+
+Here's an example configuration object.
+
+You can provide it as [preset options](#ex-config-preset) or [plugin options](#ex-config-plugin).
+
+:::tip
+
+Most Docusaurus users configure this plugin through the [preset options](#ex-config-preset).
+
+:::
+
+```js
+const config = {
+  trackingID: 'UA-141789564-1',
+  anonymizeIP: true,
+};
+```
+
+### Preset options {#ex-config-preset}
+
+If you use a preset, configure this plugin through the [preset options](presets.md#docusauruspreset-classic):
+
+```js title="docusaurus.config.js"
+module.exports = {
+  presets: [
+    [
+      '@docusaurus/preset-classic',
+      {
+        // highlight-start
+        googleAnalytics: {
+          trackingID: 'UA-141789564-1',
+          anonymizeIP: true,
+        },
+        // highlight-end
+      },
+    ],
+  ],
+};
+```
+
+### Plugin options {#ex-config-plugin}
+
+If you are using a standalone plugin, provide options directly to the plugin:
+
+```js title="docusaurus.config.js"
+module.exports = {
+  plugins: [
+    [
+      '@docusaurus/plugin-google-analytics',
+      // highlight-start
+      {
+        trackingID: 'UA-141789564-1',
+        anonymizeIP: true,
+      },
+      // highlight-end
+    ],
+  ],
+};
+```
diff --git a/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-gtag.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-gtag.md
new file mode 100644
index 0000000000..756dc83fd4
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-google-gtag.md
@@ -0,0 +1,100 @@
+---
+sidebar_position: 7
+id: plugin-google-gtag
+title: '📦 plugin-google-gtag'
+slug: '/api/plugins/@docusaurus/plugin-google-gtag'
+---
+
+The default [Global Site Tag (gtag.js)](https://developers.google.com/analytics/devguides/collection/gtagjs/) plugin. It is a JavaScript tagging framework and API that allows you to send event data to Google Analytics, Google Ads, and Google Marketing Platform, **in the production build**. This section describes how to configure a Docusaurus site to enable global site tag for Google Analytics.
+
+:::tip
+
+You can use [Google's Tag Assistant](https://tagassistant.google.com/) tool to check if your gtag is set up correctly!
+
+:::
+
+## Installation {#installation}
+
+```bash npm2yarn
+npm install --save @docusaurus/plugin-google-gtag
+```
+
+:::tip
+
+If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
+
+:::
+
+## Configuration {#configuration}
+
+Accepted fields:
+
+<small>
+
+| Name | Type | Default | Description |
+| --- | --- | --- | --- |
+| `trackingID` | `string` | **Required** | The tracking ID of your gtag service. |
+| `anonymizeIP` | `boolean` | `false` | Whether the IP should be anonymized when sending requests. |
+
+</small>
+
+## Example configuration {#ex-config}
+
+Here's an example configuration object.
+
+You can provide it as [preset options](#ex-config-preset) or [plugin options](#ex-config-plugin).
+
+:::tip
+
+Most Docusaurus users configure this plugin through the [preset options](#ex-config-preset).
+
+:::
+
+```js
+const config = {
+  trackingID: 'UA-141789564-1',
+  anonymizeIP: true,
+};
+```
+
+### Preset options {#ex-config-preset}
+
+If you use a preset, configure this plugin through the [preset options](presets.md#docusauruspreset-classic):
+
+```js title="docusaurus.config.js"
+module.exports = {
+  presets: [
+    [
+      '@docusaurus/preset-classic',
+      {
+        // highlight-start
+        gtag: {
+          trackingID: 'UA-141789564-1',
+          anonymizeIP: true,
+        },
+        // highlight-end
+      },
+    ],
+  ],
+};
+```
+
+### Plugin options {#ex-config-plugin}
+
+If you are using a standalone plugin, provide options directly to the plugin:
+
+```js title="docusaurus.config.js"
+module.exports = {
+  plugins: [
+    [
+      '@docusaurus/plugin-google-gtag',
+      // highlight-start
+      {
+        trackingID: 'UA-141789564-1',
+        anonymizeIP: true,
+      },
+      // highlight-end
+    ],
+  ],
+};
+```
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-ideal-image.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-ideal-image.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-ideal-image.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-ideal-image.md
index 737d4ee417..363946e698 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-ideal-image.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-ideal-image.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 8
 id: plugin-ideal-image
 title: '📦 plugin-ideal-image'
 slug: '/api/plugins/@docusaurus/plugin-ideal-image'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-pwa.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-pwa.md
similarity index 99%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-pwa.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-pwa.md
index 7894d3ec2f..1a7ab67bbe 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-pwa.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-pwa.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 9
 id: plugin-pwa
 title: '📦 plugin-pwa'
 slug: '/api/plugins/@docusaurus/plugin-pwa'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-sitemap.md b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-sitemap.md
similarity index 97%
rename from website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-sitemap.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-sitemap.md
index 4631b9fc9d..5e61a00b76 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-sitemap.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/plugins/plugin-sitemap.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 10
 id: plugin-sitemap
 title: '📦 plugin-sitemap'
 slug: '/api/plugins/@docusaurus/plugin-sitemap'
diff --git a/website/versioned_docs/version-2.0.0-beta.11/api/themes/_category_.yml b/website/versioned_docs/version-2.0.0-beta.11/api/themes/_category_.yml
new file mode 100644
index 0000000000..a0ceda5d59
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/themes/_category_.yml
@@ -0,0 +1,5 @@
+label: Themes
+position: 3
+link:
+  type: doc
+  id: themes-overview # Dogfood using a "local id"
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/themes/overview.md b/website/versioned_docs/version-2.0.0-beta.11/api/themes/overview.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/themes/overview.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/themes/overview.md
index 8a2ee6b50f..6047040db0 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/themes/overview.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/themes/overview.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 0
 id: themes-overview
 title: 'Docusaurus themes'
 sidebar_label: Themes overview
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-classic.md b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-classic.md
similarity index 95%
rename from website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-classic.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-classic.md
index 3b5a3a764c..e99a320f13 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-classic.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-classic.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 2
 id: theme-classic
 title: '📦 theme-classic'
 slug: '/api/themes/@docusaurus/theme-classic'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-configuration.md b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-configuration.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-configuration.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-configuration.md
index 013acbabba..4023f10ab1 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-configuration.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-configuration.md
@@ -1,6 +1,8 @@
 ---
+sidebar_position: 1
 id: theme-configuration
 title: 'Theme configuration'
+sidebar_label: 'Configuration'
 slug: '/api/themes/configuration'
 toc_max_heading_level: 4
 ---
@@ -95,9 +97,9 @@ module.exports = {
 };
 ```
 
-### Metadatas {#metadatas}
+### Metadata {#metadata}
 
-You can configure additional html metadatas (and override existing ones).
+You can configure additional html metadata (and override existing ones).
 
 Accepted fields:
 
@@ -105,7 +107,7 @@ Accepted fields:
 
 | Name | Type | Default | Description |
 | --- | --- | --- | --- |
-| `metadatas` | `Metadata[]` | `[]` | Any field will be directly passed to the `<meta />` tag. Possible fields include `id`, `name`, `property`, `content`, `itemprop`, etc. |
+| `metadata` | `Metadata[]` | `[]` | Any field will be directly passed to the `<meta />` tag. Possible fields include `id`, `name`, `property`, `content`, `itemprop`, etc. |
 
 </APITable>
 
@@ -115,7 +117,7 @@ Example configuration:
 module.exports = {
   themeConfig: {
     // highlight-next-line
-    metadatas: [{name: 'twitter:card', content: 'summary'}],
+    metadata: [{name: 'twitter:card', content: 'summary'}],
   },
 };
 ```
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-live-codeblock.md b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-live-codeblock.md
similarity index 97%
rename from website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-live-codeblock.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-live-codeblock.md
index 568d18d08e..71e04a33ae 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-live-codeblock.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-live-codeblock.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 3
 id: theme-live-codeblock
 title: '📦 theme-live-codeblock'
 slug: '/api/themes/@docusaurus/theme-live-codeblock'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-search-algolia.md b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-search-algolia.md
similarity index 97%
rename from website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-search-algolia.md
rename to website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-search-algolia.md
index 753d8ca66e..e0cee6d8f9 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/api/themes/theme-search-algolia.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/api/themes/theme-search-algolia.md
@@ -1,4 +1,5 @@
 ---
+sidebar_position: 4
 id: theme-search-algolia
 title: '📦 theme-search-algolia'
 slug: '/api/themes/@docusaurus/theme-search-algolia'
diff --git a/website/versioned_docs/version-2.0.0-beta.9/assets/docusaurus-asset-example-banner.png b/website/versioned_docs/version-2.0.0-beta.11/assets/docusaurus-asset-example-banner.png
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/assets/docusaurus-asset-example-banner.png
rename to website/versioned_docs/version-2.0.0-beta.11/assets/docusaurus-asset-example-banner.png
diff --git a/website/versioned_docs/version-2.0.0-beta.9/assets/docusaurus-asset-example.docx b/website/versioned_docs/version-2.0.0-beta.11/assets/docusaurus-asset-example.docx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/assets/docusaurus-asset-example.docx
rename to website/versioned_docs/version-2.0.0-beta.11/assets/docusaurus-asset-example.docx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/assets/docusaurus-asset-example.xyz b/website/versioned_docs/version-2.0.0-beta.11/assets/docusaurus-asset-example.xyz
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/assets/docusaurus-asset-example.xyz
rename to website/versioned_docs/version-2.0.0-beta.11/assets/docusaurus-asset-example.xyz
diff --git a/website/versioned_docs/version-2.0.0-beta.9/blog.mdx b/website/versioned_docs/version-2.0.0-beta.11/blog.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/blog.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/blog.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/browser-support.md b/website/versioned_docs/version-2.0.0-beta.11/browser-support.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/browser-support.md
rename to website/versioned_docs/version-2.0.0-beta.11/browser-support.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/cli.md b/website/versioned_docs/version-2.0.0-beta.11/cli.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/cli.md
rename to website/versioned_docs/version-2.0.0-beta.11/cli.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/configuration.md b/website/versioned_docs/version-2.0.0-beta.11/configuration.md
similarity index 72%
rename from website/versioned_docs/version-2.0.0-beta.9/configuration.md
rename to website/versioned_docs/version-2.0.0-beta.11/configuration.md
index 58e21652ce..5192e40264 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/configuration.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/configuration.md
@@ -48,6 +48,65 @@ module.exports = {
 };
 ```
 
+:::tip
+
+Docusaurus supports **module shorthands**, allowing you to simplify the above configuration as:
+
+```js title="docusaurus.config.js"
+module.exports = {
+  // ...
+  plugins: ['content-blog', 'content-pages'],
+  themes: ['classic'],
+};
+```
+
+<details>
+
+<summary>How are shorthands resolved?</summary>
+
+When it sees a plugin / theme / preset name, it tries to load one of the following, in that order:
+
+- `{name}`
+- `@docusaurus/{type}-{name}`
+- `docusaurus-{type}-{name}`,
+
+where `type` is one of `'preset'`, `'theme'`, `'plugin'`, depending on which field the module name is declared in. The first module name that's successfully found is loaded.
+
+If the name is scoped (beginning with `@`), the name is first split into scope and package name by the first slash:
+
+```
+@scope
+^----^
+ scope  (no name!)
+
+@scope/awesome
+^----^ ^-----^
+ scope   name
+
+@scope/awesome/main
+^----^ ^----------^
+ scope     name
+```
+
+If the name is not specified, `{scope}/docusaurus-{type}` is loaded. Otherwise, the following are attempted:
+
+- `{scope}/{name}`
+- `{scope}/docusaurus-{type}-{name}`
+
+Below are some examples, for a plugin registered in the `plugins` field. Note that unlike [ESLint](https://eslint.org/docs/user-guide/configuring/plugins#configuring-plugins) or [Babel](https://babeljs.io/docs/en/options#name-normalization) where a consistent naming convention for plugins is mandated, Docusaurus permits greater naming freedom, so the resolutions are not certain, but follows the priority defined above.
+
+| Declaration | May be resolved as |
+| --- | --- |
+| `awesome` | `docusaurus-plugin-awesome` |
+| `sitemap` | [`@docusaurus/plugin-sitemap`](./api/plugins/plugin-sitemap.md) |
+| `@mycompany` | `@mycompany/docusaurus-plugin` (the only possible resolution!) |
+| `@mycompany/awesome` | `@mycompany/docusaurus-plugin-awesome` |
+| `@mycompany/awesome/web` | `@mycompany/docusaurus-plugin-awesome/web` |
+
+</details>
+
+:::
+
 They can also be loaded from local directories:
 
 ```js title="docusaurus.config.js"
@@ -66,7 +125,7 @@ module.exports = {
   // ...
   plugins: [
     [
-      '@docusaurus/plugin-content-blog',
+      'content-blog',
       {
         path: 'blog',
         routeBasePath: 'blog',
@@ -74,7 +133,7 @@ module.exports = {
         // ...
       },
     ],
-    '@docusaurus/plugin-content-pages',
+    'content-pages',
   ],
 };
 ```
@@ -100,6 +159,12 @@ module.exports = {
 };
 ```
 
+:::tip
+
+The `presets: [['classic', {...}]]` shorthand works as well.
+
+:::
+
 For further help configuring themes, plugins, and presets, see [Using Themes](using-themes.md), [Using Plugins](using-plugins.md), and [Using Presets](presets.md).
 
 ### Custom configurations {#custom-configurations}
diff --git a/website/versioned_docs/version-2.0.0-beta.11/deployment.mdx b/website/versioned_docs/version-2.0.0-beta.11/deployment.mdx
new file mode 100644
index 0000000000..649151e36e
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-beta.11/deployment.mdx
@@ -0,0 +1,726 @@
+---
+id: deployment
+title: Deployment
+---
+
+To build the static files of your website for production, run:
+
+```bash npm2yarn
+npm run build
+```
+
+Once it finishes, the static files will be generated within the `build` directory.
+
+:::note
+
+The only responsibility of Docusaurus is to build your site and emit static files in `build`.
+
+It is now up to you to choose how to host those static files.
+
+:::
+
+You can deploy your site to static site hosting services such as [Vercel](https://vercel.com/), [GitHub Pages](https://pages.github.com/), [Netlify](https://www.netlify.com/), [Render](https://render.com/docs/static-sites), [Surge](https://surge.sh/help/getting-started-with-surge)...
+
+A Docusaurus site is statically rendered, and it can generally work without JavaScript!
+
+## Configuration {#configuration}
+
+The following parameters are required in `docusaurus.config.js` in order for Docusaurus to optimize routing and serve files from the correct location:
+
+| Name | Description |
+| --- | --- |
+| `url` | URL for your site. For a site deployed at `https://my-org.com/my-project/`, `url` is `https://my-org.com/`. |
+| `baseUrl` | Base URL for your project, with a trailing slash. For a site deployed at `https://my-org.com/my-project/`, `baseUrl` is `/my-project/`. |
+
+## Testing your Build Locally {#testing-build-locally}
+
+It is important to test your build locally before deploying to production. Docusaurus provides a [`docusaurus serve`](cli.md#docusaurus-serve-sitedir) command for that:
+
+```bash npm2yarn
+npm run serve
+```
+
+By default, this will load your site at [http://localhost:3000/](http://localhost:3000/).
+
+## Trailing slash configuration {#trailing-slashes}
+
+Docusaurus has a [`trailingSlash` config](./api/docusaurus.config.js.md#trailing-slash), to allow customizing URLs/links and emitted filename patterns.
+
+The default value generally works fine. Unfortunately, each static hosting provider has a **different behavior**, and deploying the exact same site to various hosts can lead to distinct results. Depending on your host, it can be useful to change this config.
+
+:::tip
+
+Use [slorber/trailing-slash-guide](https://github.com/slorber/trailing-slash-guide) to understand better the behavior of your host and configure `trailingSlash` appropriately.
+
+:::
+
+## Choosing a hosting provider
+
+There are a few common hosting options:
+
+- [Self hosting](#self-hosting) with an HTTP server like Apache2 or Nginx;
+- Jamstack providers, e.g. [Netlify](#deploying-to-netlify) and [Vercel](#deploying-to-vercel). We will use them as references, but the same reasoning can apply to other providers.
+- [GitHub Pages](#deploying-to-github-pages). (By definition, it is also Jamstack, but we compare it separately.)
+
+If you are unsure of which one to choose, ask the following questions:
+
+<details>
+
+<summary>
+  How much resource (person-hours, money) am I willing to invest in this?
+</summary>
+
+- 🔴 Self-hosting is the hardest to set up—you would usually need an experienced person to manage this. Cloud services is almost never free, and setting up an on-site server and connecting it to the WAN can be more costly.
+- 🟢 Jamstack providers can help you set up a working website in almost no time and offers features like server-side redirects that are easily configurable. Many providers offer generous build time quota even for free plans that you would almost never exceed. However, it's still ultimately limited—you would need to pay once you hit the limit. Check the pricing page of your provider for details.
+- 🟡 The GitHub Pages deployment workflow can be tedious to set up. (Evidence: see the length of [Deploying to GitHub Pages](#deploying-to-github-pages)!) However, this service (including build and deployment) is always free for public repositories, and we have detailed instructions to help you make it work.
+
+</details>
+
+<details>
+
+<summary>How much server-side configuration would I need?</summary>
+
+- 🟢 With self-hosting, you have access to the entire server's configuration. You can configure the virtual host to serve different content based on the request URL; you can do complicated server-side redirects; you can put part of the site behind authentication... If you need a lot of server-side features, self-host your website.
+- 🟡 Jamstack usually offers some server-side configurations, e.g. URLs formatting (trailing slashes), server-side redirects...
+- 🔴 GitHub Pages doesn't expose server-side configurations besides enforcing HTTPS and setting CNAME.
+
+</details>
+
+<details>
+
+<summary>Do I have needs to cooperate?</summary>
+
+- 🟡 Self-hosted services can achieve the same effect as Netlify, but with much more heavy-lifting. Usually, you would have a specific person who looks after the deployment, and the workflow won't be very git-based as opposed to the other two options.
+- 🟢 Netlify and Vercel have deploy previews for every pull request, which is useful for a team to review work before merging to production. You can also manage a team with different member access to the deployment.
+- 🟡 GitHub Pages cannot do deploy previews in a non-convoluted way. One repo can only be associated with one site deployment. On the other hand, you can control who has write access to the site's deployment.
+
+</details>
+
+There isn't a silver bullet. You need to weigh your needs and resources before making a choice.
+
+## Self-Hosting {#self-hosting}
+
+Docusaurus can be self-hosted using [`docusaurus serve`](cli.md#docusaurus-serve-sitedir). Change port using `--port` and `--host` to change host.
+
+```bash npm2yarn
+npm run serve -- --build --port 80 --host 0.0.0.0
+```
+
+:::warning
+
+It is not the best option, compared to a static hosting provider / CDN.
+
+:::
+
+:::warning
+
+In the following sections, we will introduce a few common hosting providers and how they should be configured to deploy Docusaurus sites most efficiently. Some of the writeups are provided by external contributors. Docusaurus is not interest-related with any of the services. The documentation may not be up-to-date: recent changes in their API may not be reflected on our side. If you see outdated content, PRs are welcome.
+
+For the same concern of up-to-datedness, we have stopped accepting PRs adding new hosting options. You can, however, publish your writeup on a separate site (e.g. your blog, or the provider's official website), and ask us to include a link to your writeup.
+
+:::
+
+## Deploying to Netlify {#deploying-to-netlify}
+
+To deploy your Docusaurus 2 sites to [Netlify](https://www.netlify.com/), first make sure the following options are properly configured:
+
+```js {2-3} title="docusaurus.config.js"
+module.exports = {
+  url: 'https://docusaurus-2.netlify.app', // Url to your site with no trailing slash
+  baseUrl: '/', // Base directory of your site relative to your repo
+  // ...
+};
+```
+
+Then, [create your site with Netlify](https://app.netlify.com/start).
+
+While you set up the site, specify the build commands and directories as follows:
+
+- build command: `npm run build`
+- build directory: `build`
+
+If you did not configure these build options, you may still go to "Site settings" -> "Build and deploy" after your site is created.
+
+Once properly configured with the above options, your site should deploy and automatically redeploy upon merging to your deploy branch, which defaults to `main`.
+
+:::caution
+
+Some Docusaurus sites put the `docs` folder outside of `website` (most likely former Docusaurus v1 sites):
+
+```bash
+repo           # git root
+├── docs       # md files
+└── website    # docusaurus root
+```
+
+If you decide to use the `website` folder as Netlify's base directory, Netlify will not trigger builds when you update the `docs` folder, and you need to configure a [custom `ignore` command](https://docs.netlify.com/configure-builds/common-configurations/ignore-builds/):
+
+```toml title="website/netlify.toml"
+[build]
+  ignore = "git diff --quiet $CACHED_COMMIT_REF $COMMIT_REF . ../docs/"
+```
+
+:::
+
+:::warning
+
+By default, Netlify adds trailing slashes to Docusaurus URLs.
+
+It is recommended to disable the Netlify setting `Post Processing > Asset Optimization > Pretty Urls` to prevent lowercased URLs, unnecessary redirects, and 404 errors.
+
+**Be very careful**: the `Disable asset optimization` global checkbox is broken and does not really disable the `Pretty URLs` setting in practice. Please make sure to **uncheck it independently**.
+
+If you want to keep the `Pretty Urls` Netlify setting on, adjust the `trailingSlash` Docusaurus config appropriately.
+
+Refer to [slorber/trailing-slash-guide](https://github.com/slorber/trailing-slash-guide) for more information.
+
+:::
+
+## Deploying to Vercel {#deploying-to-vercel}
+
+Deploying your Docusaurus project to [Vercel](https://vercel.com/) will provide you with [various benefits](https://vercel.com/) in the areas of performance and ease of use.
+
+To deploy your Docusaurus project with a [Vercel for Git Integration](https://vercel.com/docs/git-integrations), make sure it has been pushed to a Git repository.
+
+Import the project into Vercel using the [Import Flow](https://vercel.com/import/git). During the import, you will find all relevant options preconfigured for you; however, you can choose to change any of these options, a list of which can be found [here](https://vercel.com/docs/build-step#build-&-development-settings).
+
+After your project has been imported, all subsequent pushes to branches will generate [Preview Deployments](https://vercel.com/docs/platform/deployments#preview), and all changes made to the [Production Branch](https://vercel.com/docs/git-integrations#production-branch) (usually "main" or "master") will result in a [Production Deployment](https://vercel.com/docs/platform/deployments#production).
+
+## Deploying to GitHub Pages {#deploying-to-github-pages}
+
+Docusaurus provides an easy way to publish to [GitHub Pages](https://pages.github.com/), which comes for free with every GitHub repository.
+
+### Overview {#github-pages-overview}
+
+Usually, there are two repositories (at least, two branches) involved in a publishing process: the branch containing the source files, and the branch containing the build output to be served with GitHub Pages. In the following tutorial they will be referred to as **"source"** and **"deployment"**, respectively.
+
+Each GitHub repository is associated with a GitHub Pages service. If the deployment repository is called `my-org/my-project` (where `my-org` is the organization name or username), the deployed site will appear at `https://my-org.github.io/my-project/`. Specially, if the deployment repository is called `my-org/my-org.github.io` (the _organization GitHub Pages repo_), the site will appear at `https://my-org.github.io/`.
+
+:::info
+
+In case you want to use your custom domain for GitHub Pages, create a `CNAME` file in the `static` directory. Anything within the `static` directory will be copied to the root of the `build` directory for deployment. When using a custom domain, you should be able to move back from `baseUrl: '/projectName/'` to `baseUrl: '/'`, and also set your `url` to your custom domain.
+
+You may refer to GitHub Pages' documentation [User, Organization, and Project Pages](https://help.github.com/en/articles/user-organization-and-project-pages) for more details.
+
+:::
+
+GitHub Pages picks up deploy-ready files (the output from `docusaurus build`) from the default branch (`master` / `main`, usually) or the `gh-pages` branch, and either from the root or the `/docs` folder. You can configure that through `Settings > Pages` in your repository. This branch will be called the "deployment branch".
+
+We provide a `docusaurus deploy` command that helps you deploy your site from the source branch to the deployment branch in one command: clone, build, and commit.
+
+### `docusaurus.config.js` settings {#docusaurusconfigjs-settings}
+
+First, modify your `docusaurus.config.js` and add the following params:
+
+| Name | Description |
+| --- | --- |
+| `organizationName` | The GitHub user or organization that owns the deployment repository. |
+| `projectName` | The name of the deployment repository. |
+| `deploymentBranch` | The name of deployment branch. Defaults to `'gh-pages'` for non-organization GitHub Pages repos (`projectName` not ending in `.github.io`). Otherwise, this needs to be explicit as a config field or environment variable. |
+
+These fields also have their environment variable counterparts, which have a higher priority: `ORGANIZATION_NAME`, `PROJECT_NAME`, and `DEPLOYMENT_BRANCH`.
+
+:::caution
+
+GitHub Pages adds a trailing slash to Docusaurus URLs by default. It is recommended to set a `trailingSlash` config (`true` or `false`, not `undefined`).
+
+:::
+
+Example:
+
+```jsx {3-6} title="docusaurus.config.js"
+module.exports = {
+  // ...
+  url: 'https://endiliey.github.io', // Your website URL
+  baseUrl: '/',
+  projectName: 'endiliey.github.io',
+  organizationName: 'endiliey',
+  trailingSlash: false,
+  // ...
+};
+```
+
+:::warning
+
+By default, GitHub Pages runs published files through [Jekyll](https://jekyllrb.com/). Since Jekyll will discard any files that begin with `_`, it is recommended that you disable Jekyll by adding an empty file named `.nojekyll` file to your `static` directory.
+
+:::
+
+### Environment settings {#environment-settings}
+
+| Name | Description |
+| --- | --- |
+| `USE_SSH` | Set to `true` to use SSH instead of the default HTTPS for the connection to the GitHub repo. If the source repo URL is an SSH URL (e.g. `git@github.com:facebook/docusaurus.git`), `USE_SSH` is inferred to be `true`. |
+| `GIT_USER` | The username for a GitHub account that **has push access to the deployment repo**. For your own repositories, this will usually be your GitHub username. Required if not using SSH, and ignored otherwise. |
+| `GIT_PASS` | Personal access token of the git user (specified by `GIT_USER`), to facilitate non-interactive deployment (e.g. continuous deployment) |
+| `CURRENT_BRANCH` | The source branch. Usually, the branch will be `main` or `master`, but it could be any branch except for `gh-pages`. If nothing is set for this variable, then the current branch from which `docusaurus deploy` is invoked will be used. |
+
+GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment variable:
+
+| Name          | Description                                     |
+| ------------- | ----------------------------------------------- |
+| `GITHUB_HOST` | The domain name of your GitHub enterprise site. |
+| `GITHUB_PORT` | The port of your GitHub enterprise site.        |
+
+### Deploy {#deploy}
+
+Finally, to deploy your site to GitHub Pages, run:
+
+````mdx-code-block
+<Tabs>
+<TabItem value="bash" label="Bash">
+
+```bash
+GIT_USER=<GITHUB_USERNAME> yarn deploy
+```
+
+</TabItem>
+<TabItem value="windows" label="Windows">
+
+```batch
+cmd /C "set "GIT_USER=<GITHUB_USERNAME>" && yarn deploy"
+```
+
+</TabItem>
+<TabItem value="powershell" label="PowerShell">
+
+```powershell
+cmd /C 'set "GIT_USER=<GITHUB_USERNAME>" && yarn deploy'
+```
+
+</TabItem>
+</Tabs>
+````
+
+:::caution
+
+Beginning in August 2021, GitHub requires every command-line sign-in to use the **personal access token** instead of the password. When GitHub prompts for your password, enter the PAT instead. See the [GitHub documentation](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) for more information.
+
+Alternatively, you can use SSH (`USE_SSH=true`) to login.
+
+:::
+
+### Triggering deployment with GitHub Actions {#triggering-deployment-with-github-actions}
+
+[GitHub Actions](https://help.github.com/en/actions) allow you to automate, customize, and execute your software development workflows right in your repository.
+
+The workflow examples below assume your website source resides in the `main` branch of your repository (the _source branch_ is `main`), under a folder called `website/`, and your [publishing source](https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) is configured for the `gh-pages` branch (the _deployment branch_ is `gh-pages`).
+
+Our goal is that:
+
+1. When a new pull request is made to `main` and updates `website/`, there's an action that ensures the site builds successfully, without actually deploying. This job will be called `test-deploy`.
+2. When a pull request is merged to the `main` branch or someone pushes to the `main` branch directly and `website/` is updated, it will be built and deployed to the `gh-pages` branch. After that, the new built output will be served on the GitHub Pages site. This job will be called `deploy`.
+
+Here are two approaches to deploying your docs with GitHub Actions. Based on the location of your deployment branch (`gh-pages`), choose the relevant tab below:
+
+- Source repo and deployment repo are the **same** repository.
+- The deployment repo is a **remote** repository, different from the source.
+
+````mdx-code-block
+<Tabs>
+<TabItem value="same" label="Same">
+
+While you can have both jobs defined in the same workflow file, the `deploy` job will always be listed as skipped in the PR check suite status. That's added noise providing no value to the review process, and as you cannot easily share common snippets, it is better to manage them as separate workflows instead.
+
+We will use a popular third-party deployment action: [peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus).
+
+<details>
+
+<summary>GitHub action files</summary>
+
+Add these two workflow files:
+
+:::warning
+
+These files assume you are using yarn. If you use npm, change `cache: yarn`, `yarn install --frozen-lockfile`, `yarn build` to `cache: npm`, `npm ci`, `npm run build` accordingly.
+
+:::
+
+```yml title=".github/workflows/deploy.yml"
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+    paths: [website/**]
+
+jobs:
+  deploy:
+    name: Deploy to GitHub Pages
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14.x
+          cache: yarn
+      - name: Build website
+        working-directory: website
+        run: |
+          yarn install --frozen-lockfile
+          yarn build
+
+      # Popular action to deploy to GitHub Pages:
+      # Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          # Build output to publish to the `gh-pages` branch:
+          publish_dir: ./website/build
+          # Assign commit authorship to the official GH-Actions bot for deploys to `gh-pages` branch:
+          # https://github.com/actions/checkout/issues/13#issuecomment-724415212
+          # The GH actions bot is used by default if you didn't specify the two fields.
+          # You can swap them out with your own user credentials.
+          user_name: github-actions[bot]
+          user_email: 41898282+github-actions[bot]@users.noreply.github.com
+```
+
+```yml title=".github/workflows/test-deploy.yml"
+name: Test deployment
+
+on:
+  pull_request:
+    branches: [main]
+    paths: [website/**]
+
+jobs:
+  test-deploy:
+    name: Test deployment
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14.x
+          cache: yarn
+      - name: Test build
+        working-directory: website
+        run: |
+          yarn install --frozen-lockfile
+          yarn build
+```
+
+</details>
+
+</TabItem>
+<TabItem value="remote" label="Remote">
+
+A cross-repo publish is more difficult to set up, because you need to push to another repo with permission checks. We will be using SSH to do the authentication.
+
+1. Generate a new [SSH key](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
+2. By default, your public key should have been created in `~/.ssh/id_rsa.pub`; otherwise, use the name you've provided in the previous step to add your key to [GitHub deploy keys](https://developer.github.com/v3/guides/managing-deploy-keys/).
+3. Copy the key to clipboard with `xclip -sel clip < ~/.ssh/id_rsa.pub` and paste it as a [deploy key](https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys) in your repository. Copy the file content if the command line doesn't work for you. Check the box for `Allow write access` before saving your deployment key.
+4. You'll need your private key as a [GitHub secret](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) to allow Docusaurus to run the deployment for you.
+5. Copy your private key with `xclip -sel clip < ~/.ssh/id_rsa` and paste a GitHub secret with the name `GH_PAGES_DEPLOY`. Copy the file content if the command line doesn't work for you. Save your secret.
+6. Create your [documentation workflow file](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#creating-a-workflow-file) in `.github/workflows/`. In this example it's `deploy.yml`.
+
+<details>
+
+<summary>GitHub action file</summary>
+
+:::warning
+
+Please make sure that you replace `actions@github.com` with your GitHub email and `gh-actions` with your name.
+
+This file assumes you are using yarn. If you use npm, change `cache: yarn`, `yarn install --frozen-lockfile`, `yarn build` to `cache: npm`, `npm ci`, `npm run build` accordingly.
+
+:::
+
+```yml title=".github/workflows/deploy.yml"
+name: Deploy to GitHub Pages
+
+on:
+  pull_request:
+    branches: [main]
+  push:
+    branches: [main]
+
+jobs:
+  test-deploy:
+    if: github.event_name != 'push'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14.x
+          cache: yarn
+      - name: Test deployment
+        run: |
+          yarn install --frozen-lockfile
+          yarn build
+  deploy:
+    if: github.event_name != 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14.x
+          cache: yarn
+      - uses: webfactory/ssh-agent@v0.5.0
+        with:
+          ssh-private-key: ${{ secrets.GH_PAGES_DEPLOY }}
+      - name: Deploy to GitHub Pages
+        env:
+          USE_SSH: true
+        run: |
+          git config --global user.email "actions@github.com"
+          git config --global user.name "gh-actions"
+          yarn install --frozen-lockfile
+          yarn deploy
+```
+
+</details>
+
+</TabItem>
+</Tabs>
+````
+
+### Triggering deployment with Travis CI {#triggering-deployment-with-travis-ci}
+
+Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and deploying changes to your website. All you need to do to automate the deployment of your website is to invoke the `yarn deploy` script whenever your website is updated. The following section covers how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider.
+
+1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). When creating the token, grant it the `repo` scope so that it has the permissions it needs.
+2. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate.
+3. Open your Travis CI dashboard. The URL looks like `https://travis-ci.com/USERNAME/REPO`, and navigate to the `More options > Setting > Environment Variables` section of your repository.
+4. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username).
+5. Create a `.travis.yml` on the root of your repository with the following:
+
+```yml title=".travis.yml"
+language: node_js
+node_js:
+  - '14.15.0'
+branches:
+  only:
+    - main
+cache:
+  yarn: true
+script:
+  - git config --global user.name "${GH_NAME}"
+  - git config --global user.email "${GH_EMAIL}"
+  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+  - yarn install
+  - GIT_USER="${GH_NAME}" yarn deploy
+```
+
+Now, whenever a new commit lands in `main`, Travis CI will run your suite of tests and if everything passes, your website will be deployed via the `yarn deploy` script.
+
+### Triggering deployment with Buddy {#triggering-deployment-with-buddy}
+
+[Buddy](https://buddy.works/) is an easy-to-use CI/CD tool that allows you to automate the deployment of your portal to different environments, including GitHub Pages.
+
+Follow these steps to create a pipeline that automatically deploys a new version of your website whenever you push changes to the selected branch of your project:
+
+1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). When creating the token, grant it the `repo` scope so that it has the permissions it needs.
+2. Sign in to your Buddy account and create a new project.
+3. Choose GitHub as your git hosting provider and select the repository with the code of your website.
+4. Using the left navigation panel, switch to the `Pipelines` view.
+5. Create a new pipeline. Define its name, set the trigger mode to `On push`, and select the branch that triggers the pipeline execution.
+6. Add a `Node.js` action.
+7. Add these commands in the action's terminal:
+
+```bash
+GIT_USER=<GH_PERSONAL_ACCESS_TOKEN>
+git config --global user.email "<YOUR_GH_EMAIL>"
+git config --global user.name "<YOUR_GH_USERNAME>"
+yarn deploy
+```
+
+After creating this simple pipeline, each new commit pushed to the branch you selected deploys your website to GitHub Pages using `yarn deploy`. Read [this guide](https://buddy.works/guides/react-docusaurus) to learn more about setting up a CI/CD pipeline for Docusaurus.
+
+### Using Azure Pipelines {#using-azure-pipelines}
+
+1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already.
+2. Create an organization and within the organization create a project and connect your repository from GitHub.
+3. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with the `repo` scope.
+4. In the project page (which looks like `https://dev.azure.com/ORG_NAME/REPO_NAME/_build` create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root.
+
+```yml title="azure-pipelines.yml"
+trigger:
+  - main
+
+pool:
+  vmImage: ubuntu-latest
+
+steps:
+  - checkout: self
+    persistCredentials: true
+
+  - task: NodeTool@0
+    inputs:
+      versionSpec: 14.x
+    displayName: Install Node.js
+
+  - script: |
+      git config --global user.name "${GH_NAME}"
+      git config --global user.email "${GH_EMAIL}"
+      git checkout -b main
+      echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
+      yarn install
+      GIT_USER="${GH_NAME}" yarn deploy
+    env:
+      GH_NAME: $(GH_NAME)
+      GH_EMAIL: $(GH_EMAIL)
+      GH_TOKEN: $(GH_TOKEN)
+    displayName: Install and build
+```
+
+### Using Drone {#using-drone}
+
+1. Create a new ssh key that will be the [deploy key](https://docs.github.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys#deploy-keys) for your project.
+2. Name your private and public keys to be specific and so that it does not overwrite your other [ssh keys](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
+3. Go to `https://github.com/USERNAME/REPO/settings/keys` and add a new deploy key by pasting in our public key you just generated.
+4. Open your Drone.io dashboard and login. The URL looks like `https://cloud.drone.io/USERNAME/REPO`.
+5. Click on the repository, click on activate repository, and add a secret called `git_deploy_private_key` with your private key value that you just generated.
+6. Create a `.drone.yml` on the root of your repository with below text.
+
+```yml title=".drone.yml"
+kind: pipeline
+type: docker
+trigger:
+  event:
+    - tag
+- name: Website
+  image: node
+  commands:
+    - mkdir -p $HOME/.ssh
+    - ssh-keyscan -t rsa github.com >> $HOME/.ssh/known_hosts
+    - echo "$GITHUB_PRIVATE_KEY" > "$HOME/.ssh/id_rsa"
+    - chmod 0600 $HOME/.ssh/id_rsa
+    - cd website
+    - yarn install
+    - yarn deploy
+  environment:
+    USE_SSH: true
+    GITHUB_PRIVATE_KEY:
+      from_secret: git_deploy_private_key
+```
+
+Now, whenever you push a new tag to GitHub, this trigger will start the drone CI job to publish your website.
+
+## Deploying to Render {#deploying-to-render}
+
+[Render](https://render.com) offers [free static site hosting](https://render.com/docs/static-sites) with fully managed SSL, custom domains, a global CDN and continuous auto-deploy from your Git repo. Get started in just a few minutes by following [Render's guide to deploying Docusaurus](https://render.com/docs/deploy-docusaurus).
+
+## Deploying to Qovery {#deploying-to-qovery}
+
+[Qovery](https://www.qovery.com) is a fully-managed cloud platform that runs on your AWS, Digital Ocean and Scaleway account where you can host static sites, backend APIs, databases, cron jobs, and all your other apps in one place.
+
+1. Create a Qovery account. Visit the [Qovery dashboard](https://console.qovery.com) to create an account if you don't already have one.
+2. Create a project.
+   - Click on **Create project** and give a name to your project.
+   - Click on **Next**.
+3. Create a new environment.
+   - Click on **Create environment** and give a name (e.g. staging, production).
+4. Add an application.
+   - Click on **Create an application**, give a name and select your GitHub or GitLab repository where your Docusaurus app is located.
+   - Define the main branch name and the root application path.
+   - Click on **Create**. After the application is created:
+   - Navigate to your application **Settings**
+   - Select **Port**
+   - Add port used by your Docusaurus application
+5. Deploy All you have to do now is to navigate to your application and click on **Deploy**.
+
+![Deploy the app](https://hub.qovery.com/img/heroku/heroku-1.png)
+
+That's it. Watch the status and wait till the app is deployed. To open the application in your browser, click on **Action** and **Open** in your application overview.
+
+## Deploying to Hostman {#deploying-to-hostman}
+
+[Hostman](https://hostman.com/) allows you to host static websites for free. Hostman automates everything, you just need to connect your repository and follow easy steps:
+
+1. Create a service.
+
+   To deploy a Docusaurus static website, click **Create** in the top-left corner of your [Dashboard](https://dashboard.hostman.com/) and choose **Front-end app or static website**.
+
+2. Select the project to deploy.
+
+   If you are logged in to Hostman with your GitHub, GitLab or Bitbucket account, at this point you will see the repository with your projects, including the private ones.
+
+   Choose the project you want to deploy. It must contain the directory with the project’s files (usually it is website or my-website).
+
+   To access a different repository, click **Connect another repository**.
+
+   If you didn’t use your Git account credentials to log in, you’ll be able to access the necessary account now, and then select the project.
+
+3. Configure the build settings.
+
+   Next, the **Website customization** window will appear. Choose the **Static website** option from the list of frameworks.
+
+   The **Directory with app** points at the directory that will contain the project's files after the build. You can leave it empty if during Step 2 you selected the repository with the contents of the website (or `my_website`) directory.
+
+   The standard build command for Docusaurus will be:
+
+   ```bash npm2yarn
+   npm run build
+   ```
+
+   You can modify the build command if needed. You can enter multiple commands separated by `&&`.
+
+4. Deploy.
+
+   Click **Deploy** to start the build process.
+
+   Once it starts, you will enter the deployment log. If there are any issues with the code, you will get warning or error messages in the log, specifying the cause of the problem. Usually, the log contains all the debugging data you'll need.
+
+   When the deployment is complete, you will receive an email notification and also see a log entry. All done! Your project is up and ready.
+
+## Deploying to Surge {#deploying-to-surge}
+
+Surge is a [static web hosting platform](https://surge.sh/help/getting-started-with-surge), it is used to deploy your Docusaurus project from the command line in a minute. Deploying your project to Surge is easy and it is also free (including a custom domain and SSL).
+
+Deploy your app in a matter of seconds using surge with the following steps:
+
+1. First, install Surge using npm by running the following command:
+   ```bash npm2yarn
+   npm install -g surge
+   ```
+2. To build the static files of your site for production in the root directory of your project, run:
+   ```bash npm2yarn
+   npm run build
+   ```
+3. Then, run this command inside the root directory of your project:
+   ```bash
+   surge build/
+   ```
+
+First-time users of Surge would be prompted to create an account from the command line(happens only once).
+
+Confirm that the site you want to publish is in the `build` directory, a randomly generated subdomain `*.surge.sh subdomain` is always given (which can be edited).
+
+### Using your domain {#using-your-domain}
+
+If you have a domain name you can deploy your site using surge to your domain using the command:
+
+```bash
+surge build/ yourdomain.com
+```
+
+Your site is now deployed for free at `subdomain.surge.sh` or `yourdomain.com` depending on the method you chose.
+
+### Setting up CNAME file {#setting-up-cname-file}
+
+Store your domain in a CNAME file for future deployments with the following command:
+
+```bash
+echo subdomain.surge.sh > CNAME
+```
+
+You can deploy any other changes in the future with the command `surge`.
+
+## Deploying to QuantCDN {#deploying-to-quantcdn}
+
+1. Install [Quant CLI](https://docs.quantcdn.io/docs/cli/get-started)
+2. Create a QuantCDN account by [signing up](https://dashboard.quantcdn.io/register)
+3. Initialize your project with `quant init` and fill in your credentials:
+   ```bash
+   quant init
+   ```
+4. Deploy your site.
+   ```bash
+   quant deploy
+   ```
+
+See [docs](https://docs.quantcdn.io/docs/cli/continuous-integration) and [blog](https://www.quantcdn.io/blog) for more examples and use cases for deploying to QuantCDN.
diff --git a/website/versioned_docs/version-2.0.0-beta.9/docusaurus-core.md b/website/versioned_docs/version-2.0.0-beta.11/docusaurus-core.md
similarity index 92%
rename from website/versioned_docs/version-2.0.0-beta.9/docusaurus-core.md
rename to website/versioned_docs/version-2.0.0-beta.11/docusaurus-core.md
index 80f9b56dc5..ab146688cf 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/docusaurus-core.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/docusaurus-core.md
@@ -8,6 +8,55 @@ Docusaurus provides some APIs on the clients that can be helpful to you when bui
 
 ## Components {#components}
 
+### `<ErrorBoundary />` {#errorboundary}
+
+This component creates a [React error boundary](https://reactjs.org/docs/error-boundaries.html).
+
+Use it to wrap components that might throw, and display a fallback when that happens instead of crashing the whole app.
+
+```jsx
+import React from 'react';
+import ErrorBoundary from '@docusaurus/ErrorBoundary';
+
+const SafeComponent = () => (
+  <ErrorBoundary
+    fallback={({error, tryAgain}) => (
+      <div>
+        <p>This component crashed because of error: {error.message}.</p>
+        <button onClick={tryAgain}>Try Again!</button>
+      </div>
+    )}>
+    <SomeDangerousComponentThatMayThrow />
+  </ErrorBoundary>
+);
+```
+
+```mdx-code-block
+import ErrorBoundaryTestButton from "@site/src/components/ErrorBoundaryTestButton"
+```
+
+:::tip
+
+To see it in action, click here: <ErrorBoundaryTestButton/>
+
+:::
+
+:::info
+
+Docusaurus uses this component to catch errors within the theme's layout, and also within the entire app.
+
+:::
+
+:::note
+
+This component doesn't catch build-time errors, and only protects against client-side render errors that can happen when using stateful React components.
+
+:::
+
+#### Props {#errorboundary-props}
+
+- `fallback`: an optional callback returning a JSX element. It will receive two props: `error`, the error that was caught, and `tryAgain`, a function (`() => void`) callback to reset the error in the component and try rendering it again.
+
 ### `<Head/>` {#head}
 
 This reusable React component will manage all of your changes to the document head. It takes plain HTML tags and outputs plain HTML tags and is beginner-friendly. It is a wrapper around [React Helmet](https://github.com/nfl/react-helmet).
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/creating-pages.md b/website/versioned_docs/version-2.0.0-beta.11/guides/creating-pages.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/creating-pages.md
rename to website/versioned_docs/version-2.0.0-beta.11/guides/creating-pages.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-create-doc.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-create-doc.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-create-doc.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-create-doc.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-introduction.md b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-introduction.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-introduction.md
rename to website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-introduction.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-markdown-features.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-markdown-features.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-markdown-features.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-markdown-features.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-multi-instance.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-multi-instance.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/docs/docs-multi-instance.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/docs/docs-multi-instance.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/sidebar.md b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/sidebar.md
similarity index 82%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/docs/sidebar.md
rename to website/versioned_docs/version-2.0.0-beta.11/guides/docs/sidebar.md
index dfc8c4175b..a844256485 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/sidebar.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/sidebar.md
@@ -1,7 +1,7 @@
 ---
 id: sidebar
 title: Sidebar
-toc_max_heading_level: 4
+toc_max_heading_level: 5
 slug: /sidebar
 ---
 
@@ -290,6 +290,7 @@ type SidebarItemCategory = {
   // Category options:
   collapsible: boolean; // Set the category to be collapsible
   collapsed: boolean; // Set the category to be initially collapsed or open by default
+  link: SidebarItemCategoryLinkDoc | SidebarItemCategoryLinkGeneratedIndex;
 };
 ```
 
@@ -335,6 +336,69 @@ module.exports = {
 
 :::
 
+#### Category links {#category-link}
+
+With category links, clicking on a category can navigate you to another page.
+
+:::tip
+
+Use category links to introduce a category of documents.
+
+:::
+
+##### Doc link {#category-doc-link}
+
+A category can link to an existing document.
+
+```js title="sidebars.js"
+module.exports = {
+  docs: [
+    {
+      type: 'category',
+      label: 'Guides',
+      // highlight-start
+      link: {type: 'doc', id: 'introduction'},
+      // highlight-end
+      items: ['pages', 'docs', 'blog', 'search'],
+    },
+  ],
+};
+```
+
+See it in action in the [i18n introduction page](../../i18n/i18n-introduction.md).
+
+##### Generated index page {#generated-index-page}
+
+You can auto-generate an index page that displays all the direct children of this category. The `slug` allows you to customize the generated page's route, which defaults to `/category/{{category name}}`.
+
+```js title="sidebars.js"
+module.exports = {
+  docs: [
+    {
+      type: 'category',
+      label: 'Guides',
+      // highlight-start
+      link: {
+        type: 'generated-index',
+        title: 'Docusaurus Guides',
+        description: 'Learn about the most important Docusaurus concepts!',
+        slug: '/category/docusaurus-guides',
+      },
+      // highlight-end
+      items: ['pages', 'docs', 'blog', 'search'],
+    },
+  ],
+};
+```
+
+See it in action in the [Docusaurus Guides pages](/docs/next/category/guides).
+
+:::tip
+
+Use `generated-index` links as a quick way to get an introductory document.
+
+:::
+
 #### Collapsible categories {#collapsible-categories}
 
 We support the option to expand/collapse categories. Categories are collapsible by default, but you can disable collapsing with `collapsible: false`.
@@ -499,13 +563,46 @@ module.exports = {
 };
 ```
 
-#### Autogenerated sidebar metadatas {#autogenerated-sidebar-metadatas}
+#### Category index convention {#category-index-convention}
+
+Docusaurus can automatically link a category to its index document.
+
+A category index document is a document following one of those filename conventions:
+
+- Named as `index` (case-insensitive): `docs/Guides/index.md`
+- Named as `README` (case-insensitive): `docs/Guides/README.mdx`
+- Same name as parent folder: `docs/Guides/Guides.md`
+
+This is equivalent to using a category with a [doc link](#category-doc-link):
+
+```js title="sidebars.js"
+module.exports = {
+  docs: [
+    // highlight-start
+    {
+      type: 'category',
+      label: 'Guides',
+      link: {type: 'doc', id: 'Guides/index'},
+      items: [],
+    },
+    // highlight-end
+  ],
+};
+```
+
+:::tip
+
+Naming your introductory document `README.md` makes it show up when browsing the folder using the GitHub interface, while using `index.md` makes the behavior more in line with how HTML files are served.
+
+:::
+
+#### Autogenerated sidebar metadata {#autogenerated-sidebar-metadata}
 
 By default, the sidebar slice will be generated in **alphabetical order** (using files and folders names).
 
-If the generated sidebar does not look good, you can assign additional metadatas to docs and categories.
+If the generated sidebar does not look good, you can assign additional metadata to docs and categories.
 
-**For docs**: use additional frontmatter:
+**For docs**: use additional front matter:
 
 ```md title="docs/tutorials/tutorial-easy.md" {1-4}
 ---
@@ -524,10 +621,22 @@ This is the easy tutorial!
 {
   "label": "Tutorial",
   "position": 3,
-  "className": "red"
+  "className": "red",
+  "link": {
+    "type": "generated-index",
+    "title": "Tutorial overview"
+  }
 }
 ```
 
+:::info
+
+If the `link` is explicitly specified, Docusaurus will not apply any [default conventions](#category-index-convention).
+
+The doc links can be specified relatively, e.g. if the category is generated with the `guides` directory, `"link": {"type": "doc", "id": "intro"}` will be resolved to the ID `guides/intro`, only falling back to `intro` if a doc with the former ID doesn't exist.
+
+:::
+
 ```yaml title="docs/tutorials/_category_.yml"
 label: 'Tutorial'
 position: 2.5 # float position is supported
@@ -566,7 +675,7 @@ By default, Docusaurus will **remove the number prefix** from the doc id, title,
 
 :::caution
 
-**Prefer using [additional metadatas](#autogenerated-sidebar-metadatas)**.
+**Prefer using [additional metadata](#autogenerated-sidebar-metadata)**.
 
 Updating a number prefix can be annoying, as it can require **updating multiple existing markdown links**:
 
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/docs/versioning.md b/website/versioned_docs/version-2.0.0-beta.11/guides/docs/versioning.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/docs/versioning.md
rename to website/versioned_docs/version-2.0.0-beta.11/guides/docs/versioning.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/_markdown-partial-example.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/_markdown-partial-example.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/_markdown-partial-example.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/_markdown-partial-example.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-admonitions.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-admonitions.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-admonitions.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-admonitions.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-assets.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-assets.mdx
similarity index 75%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-assets.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-assets.mdx
index 8bb6942788..65ba905c28 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-assets.mdx
+++ b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-assets.mdx
@@ -5,9 +5,7 @@ description: Handling assets in Docusaurus Markdown
 slug: /markdown-features/assets
 ---
 
-Sometimes you want to link to static assets directly from Markdown files, and it is convenient to co-locate the asset next to the Markdown file using it.
-
-We have setup Webpack loaders to handle most common file types, so that when you import a file, you get its url, and the asset is automatically copied to the output folder.
+Sometimes you want to link to assets (e.g. docx files, images...) directly from Markdown files, and it is convenient to co-locate the asset next to the Markdown file using it.
 
 Let's imagine the following file structure:
 
@@ -145,3 +143,16 @@ import ThemedImage from '@theme/ThemedImage';
   }}
 />
 ```
+
+## Static assets {#static-assets}
+
+If a Markdown link or image has an absolute path, the path will be seen as a file path and will be resolved from the static directories. For example, if you have configured [static directories](../../static-assets.md) to be `['public', 'static']`, then for the following image:
+
+```md title="my-doc.md"
+![An image from the static](/img/docusaurus.png)
+```
+
+Docusaurus will try to look for it in both `static/img/docusaurus.png` and `public/img/docusaurus.png`. The link will then be converted to a `require` call instead of staying as a URL. This is desirable in two regards:
+
+1. You don't have to worry about base URL, which Docusaurus will take care of when serving the asset;
+2. The image enters Webpack's build pipeline and its name will be appended by a hash, which enables browsers to aggressively cache the image and improves your site's performance.
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-code-blocks.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-code-blocks.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-code-blocks.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-code-blocks.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-head-metadatas.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-head-metadata.mdx
similarity index 55%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-head-metadatas.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-head-metadata.mdx
index 4d4c0e6fad..c48caf9fcc 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-head-metadatas.mdx
+++ b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-head-metadata.mdx
@@ -1,34 +1,34 @@
 ---
-id: head-metadatas
-title: Head Metadatas
-description: Declaring page-specific head metadatas through MDX
-slug: /markdown-features/head-metadatas
+id: head-metadata
+title: Head Metadata
+description: Declaring page-specific head metadata through MDX
+slug: /markdown-features/head-metadata
 ---
 
-# Head Metadatas
+# Head Metadata
 
-Docusaurus automatically sets useful page metadatas in `<html>`, `<head>` and `<body>` for you.
+Docusaurus automatically sets useful page metadata in `<html>`, `<head>` and `<body>` for you.
 
-It is possible to add extra metadatas (or override existing ones) by using the `<head>` tag in Markdown files:
+It is possible to add extra metadata (or override existing ones) by using the `<head>` tag in Markdown files:
 
-```md title="markdown-features-head-metadatas.mdx"
+```md title="markdown-features-head-metadata.mdx"
 ---
-id: head-metadatas
-title: Head Metadatas
+id: head-metadata
+title: Head Metadata
 ---
 
 <!-- highlight-start -->
 <head>
   <html className="some-extra-html-class" />
   <body className="other-extra-body-class" />
-  <title>Head Metadatas customized title!</title>
+  <title>Head Metadata customized title!</title>
   <meta charSet="utf-8" />
   <meta name="twitter:card" content="summary" />
-  <link rel="canonical" href="https://docusaurus.io/docs/markdown-features/head-metadatas" />
+  <link rel="canonical" href="https://docusaurus.io/docs/markdown-features/head-metadata" />
 </head>
 <!-- highlight-end -->
 
-# Head Metadatas
+# Head Metadata
 
 My text
 ```
@@ -37,10 +37,10 @@ My text
 <head>
   <html className="some-extra-html-class" />
   <body className="other-extra-body-class" />
-  <title>Head Metadatas customized title!</title>
+  <title>Head Metadata customized title!</title>
   <meta charSet="utf-8" />
   <meta name="twitter:card" content="summary" />
-  <link rel="canonical" href="https://docusaurus.io/docs/markdown-features/head-metadatas" />
+  <link rel="canonical" href="https://docusaurus.io/docs/markdown-features/head-metadata" />
 </head>
 ```
 
@@ -48,7 +48,7 @@ My text
 
 This `<head>` declaration has been added to the current Markdown doc, as a demo.
 
-Open your browser DevTools and check how this page's metadatas have been affected.
+Open your browser DevTools and check how this page's metadata have been affected.
 
 :::
 
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-headings.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-headings.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-headings.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-headings.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-inline-toc.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-inline-toc.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-inline-toc.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-inline-toc.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-intro.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-intro.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-intro.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-intro.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-math-equations.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-math-equations.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-math-equations.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-math-equations.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-plugins.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-plugins.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-plugins.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-plugins.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-react.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-react.mdx
similarity index 79%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-react.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-react.mdx
index 08aed08e3a..8be1ae86fc 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-react.mdx
+++ b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-react.mdx
@@ -5,6 +5,8 @@ description: Using the power of React in Docusaurus Markdown documents, thanks t
 slug: /markdown-features/react
 ---
 
+# MDX and React
+
 ```mdx-code-block
 import BrowserWindow from '@site/src/components/BrowserWindow';
 ```
@@ -169,3 +171,48 @@ This way, you can reuse contents among multiple pages and avoid duplicating mate
 The table-of-contents does not currently contain the imported Markdown headings. This is a technical limitation that we are trying to solve ([issue](https://github.com/facebook/docusaurus/issues/3915)).
 
 :::
+
+## Available exports
+
+Within the MDX page, the following variables are available as globals:
+
+- `frontMatter`: the front matter as a record of string keys and values;
+- `toc`: the table of contents, as a tree of headings. See also [Inline TOC](./markdown-features-inline-toc.mdx) for a more concrete use-case.
+- `contentTitle`: the Markdown title, which is the first `h1` heading in the Markdown text. It's `undefined` if there isn't one (e.g. title specified in the front matter).
+
+```jsx
+import TOCInline from '@theme/TOCInline';
+import CodeBlock from '@theme/CodeBlock';
+
+The table of contents for this page, serialized:
+
+<CodeBlock className="language-json">{JSON.stringify(toc, null, 2)}</CodeBlock>
+
+The front matter of this page:
+
+<ul>
+  {Object.entries(frontMatter).map(([key, value]) => <li key={key}><b>{key}</b>: {value}</li>)}
+</ul>
+
+<p>The title of this page is: <b>{contentTitle}</b></p>
+```
+
+```mdx-code-block
+import TOCInline from '@theme/TOCInline';
+
+<BrowserWindow>
+
+The table of contents for this page, serialized:
+
+<CodeBlock className="language-json">{JSON.stringify(toc, null, 2)}</CodeBlock>
+
+The front matter of this page:
+
+<ul>
+  {Object.entries(frontMatter).map(([key, value]) => <li key={key}><b>{key}</b>: {value}</li>)}
+</ul>
+
+<p>The title of this page is: <b>{contentTitle}</b></p>
+
+</BrowserWindow>
+```
diff --git a/website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-tabs.mdx b/website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-tabs.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/guides/markdown-features/markdown-features-tabs.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/guides/markdown-features/markdown-features-tabs.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-crowdin.mdx b/website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-crowdin.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-crowdin.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-crowdin.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-git.md b/website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-git.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-git.md
rename to website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-git.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-introduction.md b/website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-introduction.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-introduction.md
rename to website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-introduction.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-tutorial.md b/website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-tutorial.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/i18n/i18n-tutorial.md
rename to website/versioned_docs/version-2.0.0-beta.11/i18n/i18n-tutorial.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/installation.md b/website/versioned_docs/version-2.0.0-beta.11/installation.md
similarity index 97%
rename from website/versioned_docs/version-2.0.0-beta.9/installation.md
rename to website/versioned_docs/version-2.0.0-beta.11/installation.md
index 174653ea01..f7e7ba62d8 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/installation.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/installation.md
@@ -34,6 +34,8 @@ npx create-docusaurus@latest website classic
 
 If you do not specify `name` or `template`, it will prompt you for them. We recommend the `classic` template so that you can get started quickly, and it contains features found in Docusaurus 1. The `classic` template contains `@docusaurus/preset-classic` which includes standard documentation, a blog, custom pages, and a CSS framework (with dark mode support). You can get up and running extremely quickly with the classic template and customize things later on when you have gained more familiarity with Docusaurus.
 
+The `template` also accepts a git repo URL or a local file path, with the latter evaluated relative to the current working directory. The repo/folder content will be copied to the site directory.
+
 **[FB-Only]:** If you are setting up a new Docusaurus website for a Facebook open source project, use the `facebook` template instead, which comes with some useful Facebook-specific defaults:
 
 ```bash
diff --git a/website/versioned_docs/version-2.0.0-beta.9/introduction.md b/website/versioned_docs/version-2.0.0-beta.11/introduction.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/introduction.md
rename to website/versioned_docs/version-2.0.0-beta.11/introduction.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/migration/migration-automated.md b/website/versioned_docs/version-2.0.0-beta.11/migration/migration-automated.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/migration/migration-automated.md
rename to website/versioned_docs/version-2.0.0-beta.11/migration/migration-automated.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/migration/migration-manual.md b/website/versioned_docs/version-2.0.0-beta.11/migration/migration-manual.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/migration/migration-manual.md
rename to website/versioned_docs/version-2.0.0-beta.11/migration/migration-manual.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/migration/migration-overview.md b/website/versioned_docs/version-2.0.0-beta.11/migration/migration-overview.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/migration/migration-overview.md
rename to website/versioned_docs/version-2.0.0-beta.11/migration/migration-overview.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/migration/migration-translated-sites.md b/website/versioned_docs/version-2.0.0-beta.11/migration/migration-translated-sites.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/migration/migration-translated-sites.md
rename to website/versioned_docs/version-2.0.0-beta.11/migration/migration-translated-sites.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/migration/migration-versioned-sites.md b/website/versioned_docs/version-2.0.0-beta.11/migration/migration-versioned-sites.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/migration/migration-versioned-sites.md
rename to website/versioned_docs/version-2.0.0-beta.11/migration/migration-versioned-sites.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/playground.mdx b/website/versioned_docs/version-2.0.0-beta.11/playground.mdx
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/playground.mdx
rename to website/versioned_docs/version-2.0.0-beta.11/playground.mdx
diff --git a/website/versioned_docs/version-2.0.0-beta.9/presets.md b/website/versioned_docs/version-2.0.0-beta.11/presets.md
similarity index 94%
rename from website/versioned_docs/version-2.0.0-beta.9/presets.md
rename to website/versioned_docs/version-2.0.0-beta.11/presets.md
index bfde282923..e359ca404b 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/presets.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/presets.md
@@ -106,6 +106,10 @@ module.exports = {
         pages: {},
         // Will be passed to @docusaurus/plugin-content-sitemap (false to disable)
         sitemap: {},
+        // Will be passed to @docusaurus/plugin-google-gtag (only enabled when explicitly specified)
+        gtag: {},
+        // Will be passed to @docusaurus/plugin-google-analytics (only enabled when explicitly specified)
+        googleAnalytics: {},
       },
     ],
   ],
diff --git a/website/versioned_docs/version-2.0.0-beta.9/search.md b/website/versioned_docs/version-2.0.0-beta.11/search.md
similarity index 95%
rename from website/versioned_docs/version-2.0.0-beta.9/search.md
rename to website/versioned_docs/version-2.0.0-beta.11/search.md
index ce9f986996..bba3d8c8ff 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/search.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/search.md
@@ -58,14 +58,32 @@ It is highly recommended using a config similar to the [**Docusaurus 2 website c
 
 ### Connecting Algolia {#connecting-algolia}
 
-Docusaurus' own `@docusaurus/preset-classic` supports an Algolia DocSearch integration.
+Docusaurus' own `@docusaurus/preset-classic` supports Algolia DocSearch integration. If you use the classic preset, no additional installation is needed.
 
-To connect your docs with Algolia, first add the package to your website:
+<details>
+<summary>Installation steps when not using <code>@docusaurus/preset-classic</code></summary>
+
+1. Install the package:
 
 ```bash npm2yarn
 npm install --save @docusaurus/theme-search-algolia
 ```
 
+2. Register the theme in `docusaurus.config.js`:
+
+```js title="docusaurus.config.js"
+module.exports = {
+  title: 'My site',
+  // ...
+  themes: ['@docusaurus/theme-search-algolia'],
+  themeConfig: {
+    // ...
+  },
+};
+```
+
+</details>
+
 Then, add an `algolia` field in your `themeConfig`. **[Apply for DocSearch](https://docsearch.algolia.com/apply/)** to get your Algolia index and API key.
 
 ```jsx title="docusaurus.config.js"
@@ -89,9 +107,6 @@ module.exports = {
       // Optional: Specify domains where the navigation should occur through window.location instead on history.push. Useful when our Algolia config crawls multiple documentation sites and we want to navigate with window.location.href to them.
       externalUrlRegex: 'external\\.com|domain\\.com',
 
-      // Optional: see doc section below
-      appId: 'YOUR_APP_ID',
-
       // Optional: Algolia search parameters
       searchParameters: {},
 
diff --git a/website/versioned_docs/version-2.0.0-beta.11/seo.md b/website/versioned_docs/version-2.0.0-beta.11/seo.md
new file mode 100644
index 0000000000..6fe946bb91
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-beta.11/seo.md
@@ -0,0 +1,121 @@
+---
+id: seo
+title: Search engine optimization (SEO)
+sidebar_label: SEO
+keywords:
+  - seo
+  - positioning
+---
+
+Docusaurus supports search engine optimization in a variety of ways.
+
+## Global metadata {#global-metadata}
+
+Provide global meta attributes for the entire site through the [site configuration](./configuration.md#site-metadata). The metadata will all be rendered in the HTML `<head>` using the key-value pairs as the prop name and value.
+
+```js title="docusaurus.config.js"
+module.exports = {
+  themeConfig: {
+    metadata: [{name: 'keywords', content: 'cooking, blog'}],
+    // This would become <meta name="keywords" content="cooking, blog"> in the generated HTML
+  },
+};
+```
+
+Docusaurus adds some metadata out-of-the-box. For example, if you have configured [i18n](./i18n/i18n-introduction.md), you will get a [`hreflang`](https://developers.google.com/search/docs/advanced/crawling/localized-versions) alternate link.
+
+To read more about types of meta tags, visit [the MDN docs](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta).
+
+## Single page metadata {#single-page-metadata}
+
+Similar to [global metadata](#global-metadata), Docusaurus also allows for the addition of meta-information to individual pages. Follow [this guide](./guides/markdown-features/markdown-features-head-metadata.mdx) for configuring the `<head>` tag. In short:
+
+```md title="my-markdown-page.md"
+# A cooking guide
+
+<head>
+  <meta name="keywords" content="cooking, blog">
+</head>
+
+Some content...
+```
+
+```jsx title="my-react-page.jsx"
+import React from 'react';
+import Head from '@docusaurus/Head';
+
+export default function page() {
+  return (
+    <Layout title="Page" description="A React page demo">
+      <Head>
+        <meta property="og:image" content="image.png" />
+      </Head>
+      {/* ... */}
+    </Layout>
+  );
+}
+```
+
+Docusaurus automatically adds `description`, `title`, canonical URL links, and other useful metadata to each Markdown page. They are configurable through front matter:
+
+```yml
+---
+title: Title for search engines; can be different from the actual heading
+description: A short description of this page
+image: a thumbnail image to be shown in social media cards
+keywords: [keywords, describing, the main topics]
+---
+```
+
+When creating your React page, adding these fields in `Layout` would also improve SEO.
+
+## Static HTML generation {#static-html-generation}
+
+Docusaurus is a static site generator—HTML files are statically generated for every URL route, which helps search engines discover your content more easily.
+
+## Image meta description {#image-meta-description}
+
+The alt tag for an image tells the search engine what the image is about, and is used when the image can't be visually seen, e.g. when using a screen reader, or when the image is broken. Alt tags are commonly supported in Markdown.
+
+You may also add a title for your image—this doesn't impact SEO much, but is displayed as tooltip when hovering above the image, usually used to provide hints.
+
+```md
+![Docusaurus banner](./assets/docusaurus-asset-example-banner.png 'Image title')
+```
+
+![Docusaurus banner](./assets/docusaurus-asset-example-banner.png 'Image title')
+
+## Rich search information {#rich-search-information}
+
+Docusaurus blogs support [rich search results](https://search.google.com/test/rich-results) out-of-the-box to get maximum search engine experience. The information is created depending on your meta information in blog/global configuration. In order to get the benefits of the rich search information, fill in the information about the post's publish date, authors, and image, etc. Read more about the meta-information [here](./blog.mdx).
+
+## Robots file {#robots-file}
+
+To add a `robots.txt` file that regulates search engines' behavior about which should be displayed and which shouldn't, provide it as [static asset](./static-assets.md). The following would allow access to all sub-pages from all requests:
+
+```text title="static/robots.txt"
+User-agent: *
+Disallow:
+```
+
+Read more about the robots file in [the Google documentation](https://developers.google.com/search/docs/advanced/robots/intro).
+
+:::caution
+
+**Important**: the `robots.txt` file does **not** prevent HTML pages from being indexed. Use `<meta name="robots" content="noindex">` as [page metadata](#single-page-metadata) to prevent it from appearing in search results entirely.
+
+:::
+
+## Sitemap file {#sitemap-file}
+
+Docusaurus provides the [`@docusaurus/plugin-sitemap`](./api/plugins/plugin-sitemap.md) plugin, which is shipped with `preset-classic` by default. It autogenerates a `sitemap.xml` file which will be available at `https://example.com/<baseUrl>/sitemap.xml` after the production build. This sitemap metadata helps search engine crawlers crawl your site more accurately.
+
+## Human readable links {#human-readable-links}
+
+Docusaurus uses your file names as links, but you can always change that using slugs, see this [tutorial](./guides/docs/docs-introduction.md#document-id) for more details.
+
+## Structured content {#structured-content}
+
+Search engines rely on the HTML markup such as `<h2>`, `<table>`, etc., to understand the structure of your webpage. When Docusaurus renders your pages, semantic markup, e.g. `<aside>`, `<nav>`, `<main>`, are used to divide the different sections of the page, helping the search engine to locate parts like sidebar, navbar, and the main page content.
+
+Most [CommonMark](https://spec.commonmark.org/0.30/#atx-headings) syntax have their corresponding HTML tags. By using Markdown consistently in your project, you will make it easier for search engines to understand your page content.
diff --git a/website/versioned_docs/version-2.0.0-beta.9/static-assets.md b/website/versioned_docs/version-2.0.0-beta.11/static-assets.md
similarity index 61%
rename from website/versioned_docs/version-2.0.0-beta.9/static-assets.md
rename to website/versioned_docs/version-2.0.0-beta.11/static-assets.md
index 9224e65577..b37f1c6b13 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/static-assets.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/static-assets.md
@@ -3,7 +3,7 @@ id: static-assets
 title: Static Assets
 ---
 
-Every website needs assets: images, stylesheets, favicons etc. In such cases, you can create a directory named `static` at the root of your project.
+Every website needs assets: images, stylesheets, favicons etc. By default, you are suggested to put these assets in the `static` folder.
 
 Every file you put into **that directory will be copied** into the root of the generated `build` folder with the directory hierarchy preserved. E.g. if you add a file named `sun.jpg` to the static folder, it will be copied to `build/sun.jpg`.
 
@@ -12,13 +12,31 @@ This means that:
 - for site `baseUrl: '/'`, the image `/static/img/docusaurus.png` will be served at `/img/docusaurus.png`.
 - for site `baseUrl: '/subpath/'`, the image `/static/img/docusaurus.png` will be served at `/subpath/img/docusaurus.png`.
 
+You can customize the static directory sources in `docusaurus.config.js`. For example, we can add `public` as another possible path:
+
+```js title="docusaurus.config.js"
+module.exports = {
+  title: 'My site',
+  staticDirectories: ['public', 'static'],
+  // ...
+};
+```
+
+Now, all files in `public` as well as `static` will be copied to the build output.
+
 ## Referencing your static asset {#referencing-your-static-asset}
 
-You can reference assets from the `static` folder in your code using absolute paths, but this is not ideal because changing the site `baseUrl` will **break those link**s.
+In JSX, you can reference assets from the `static` folder in your code using absolute paths, but this is not ideal because changing the site `baseUrl` will **break those links**. For the image `<img src="/img/docusaurus.png" />` served at `https://example.com/test`, the browser will try to resolve it from the URL root, i.e. as `https://example.com/img/docusaurus.png`, which will fail because it's actually served at `https://example.com/test/img/docusaurus.png`.
 
 You can `import` / `require()` the static asset (recommended), or use the `useBaseUrl` utility function: both prepend the `baseUrl` to paths for you.
 
-### JSX example {#jsx-example}
+:::info
+
+In Markdown, things are different: you can stick to use absolute paths because Docusaurus actually handles them as `require` calls instead of URLs when parsing the Markdown. See [Markdown static assets](./guides/markdown-features/markdown-features-assets.mdx).
+
+:::
+
+### Examples {#examples}
 
 ```jsx title="MyComponent.js"
 import DocusaurusImageUrl from '@site/static/img/docusaurus.png';
@@ -44,30 +62,6 @@ import DocusaurusLogoWithKeytar from '@site/static/img/docusaurus_keytar.svg';
 <DocusaurusLogoWithKeytar title="Docusaurus Logo" className="logo" />;
 ```
 
-### Markdown example {#markdown-example}
-
-Markdown links and images referencing assets of the static folder will be converted to `require("@site/static/assetName.png")"`, and **the site baseUrl will be automatically prepended** for you.
-
-```md title="my-doc.md"
-![Docusaurus](/img/docusaurus.png)
-```
-
-Thanks to MDX, you can also use `useBaseUrl` utility function in Markdown files! You'd have to use html tags like `<img>` instead of the Markdown image syntax though. The syntax is exactly the same as in JSX.
-
-```jsx title="my-doc.mdx"
----
-id: my-doc
-title: My Doc
----
-
-// Add to the top of the file below the front matter.
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-...
-
-<img alt="Docusaurus with Keytar" src={useBaseUrl('/img/docusaurus_keytar.svg')} />
-```
-
 ### Caveats {#caveats}
 
 Keep in mind that:
diff --git a/website/versioned_docs/version-2.0.0-beta.9/styling-layout.md b/website/versioned_docs/version-2.0.0-beta.11/styling-layout.md
similarity index 100%
rename from website/versioned_docs/version-2.0.0-beta.9/styling-layout.md
rename to website/versioned_docs/version-2.0.0-beta.11/styling-layout.md
diff --git a/website/versioned_docs/version-2.0.0-beta.9/typescript-support.md b/website/versioned_docs/version-2.0.0-beta.11/typescript-support.md
similarity index 97%
rename from website/versioned_docs/version-2.0.0-beta.9/typescript-support.md
rename to website/versioned_docs/version-2.0.0-beta.11/typescript-support.md
index 7a8db83a8e..e4be4222e0 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/typescript-support.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/typescript-support.md
@@ -134,4 +134,4 @@ For themes that supports TypeScript theme components, you can add the `--typescr
 npm run swizzle @docusaurus/theme-classic Footer -- --typescript
 ```
 
-At this moment, the only official Docusaurus theme that supports TypeScript theme components is `@docusaurus/theme-classic`. If you are a Docusaurus theme package author who wants to add TypeScript support, see the [Lifecycle APIs docs](./lifecycle-apis.md#gettypescriptthemepath).
+At this moment, the only official Docusaurus theme that supports TypeScript theme components is `@docusaurus/theme-classic`. If you are a Docusaurus theme package author who wants to add TypeScript support, see the [Lifecycle APIs docs](./api/lifecycle-apis.md#gettypescriptthemepath).
diff --git a/website/versioned_docs/version-2.0.0-beta.9/using-plugins.md b/website/versioned_docs/version-2.0.0-beta.11/using-plugins.md
similarity index 98%
rename from website/versioned_docs/version-2.0.0-beta.9/using-plugins.md
rename to website/versioned_docs/version-2.0.0-beta.11/using-plugins.md
index 308a8c8266..5e597bc950 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/using-plugins.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/using-plugins.md
@@ -121,7 +121,7 @@ Docusaurus' implementation of the plugins system provides us with a convenient w
 
 A plugin is a function that takes two parameters: `context` and `options`.
 
-It returns a plugin instance object, containing plugin [lifecycle APIs](./lifecycle-apis.md).
+It returns a plugin instance object, containing plugin [lifecycle APIs](./api/lifecycle-apis.md).
 
 It can be defined as a function or a module.
 
@@ -206,4 +206,4 @@ interface LoadContext {
 
 #### Return value {#return-value}
 
-The returned object value should implement the [lifecycle APIs](lifecycle-apis.md).
+The returned object value should implement the [lifecycle APIs](./api/lifecycle-apis.md).
diff --git a/website/versioned_docs/version-2.0.0-beta.9/using-themes.md b/website/versioned_docs/version-2.0.0-beta.11/using-themes.md
similarity index 74%
rename from website/versioned_docs/version-2.0.0-beta.9/using-themes.md
rename to website/versioned_docs/version-2.0.0-beta.11/using-themes.md
index 2ff65c35ee..77e9f4a71d 100644
--- a/website/versioned_docs/version-2.0.0-beta.9/using-themes.md
+++ b/website/versioned_docs/version-2.0.0-beta.11/using-themes.md
@@ -182,6 +182,34 @@ Unless you want publish to npm a "theme enhancer" (like `docusaurus-theme-live-c
 
 :::
 
+<details>
+
+<summary>How are theme aliases resolved?</summary>
+
+It can be quite hard to wrap your mind around these aliases. Let's imagine the following case with a super convoluted setup where three themes/plugins and the site itself all try to define the same component. Internally, Docusaurus loads these themes as a "stack".
+
+```text
++-------------------------------------------------+
+|        `website/src/theme/CodeBlock.js`         | <-- `@theme/CodeBlock` always points to the top
++-------------------------------------------------+
+| `theme-live-codeblock/theme/CodeBlock/index.js` | <-- `@theme-original/CodeBlock` points to the topmost non-swizzled component
++-------------------------------------------------+
+|  `plugin-awesome-codeblock/theme/CodeBlock.js`  |
++-------------------------------------------------+
+|     `theme-classic/theme/CodeBlock/index.js`    | <-- `@theme-init/CodeBlock` always points to the bottom
++-------------------------------------------------+
+```
+
+The components in this "stack" are pushed in the order of `preset plugins > preset themes > plugins > themes > site`, so the swizzled component in `website/src/theme` always comes out on top because it's loaded last.
+
+`@theme/*` always points to the topmost component—when code block is swizzled, all other components requesting `@theme/CodeBlock` receive the swizzled version.
+
+`@theme-original/*` always points to the topmost non-swizzled component. That's why you can import `@theme-original/CodeBlock` in the swizzled component—it points to the next one in the "component stack", a theme-provided one. Plugin authors should not try to use this because your component could be the topmost component and cause a self-import.
+
+`@theme-init/*` always points to the bottommost component—usually this comes from the theme or plugin that first provides this component. Individual plugins / themes trying to enhance code block can safely use `@theme-init/CodeBlock` to get its basic version. Site creators should generally not use this because you likely want to enhance the _topmost_ instead of the _bottommost_ component. It's also possible that the `@theme-init/CodeBlock` alias does not exist at all—Docusaurus only creates it when it points to a different one from `@theme-original/CodeBlock`, i.e. when it's provided by more than one theme. We don't waste aliases!
+
+</details>
+
 ## Themes design {#themes-design}
 
 While themes share the exact same lifecycle methods with plugins, their implementations can look very different from those of plugins based on themes' designed objectives.
@@ -210,13 +238,13 @@ website
 
 There are two lifecycle methods that are essential to theme implementation:
 
-- [`getThemePath()`](lifecycle-apis.md#getthemepath)
-- [`getClientModules()`](lifecycle-apis.md#getclientmodules)
+- [`getThemePath()`](./api/lifecycle-apis.md#getthemepath)
+- [`getClientModules()`](./api/lifecycle-apis.md#getclientmodules)
 
-These lifecycle method are not essential but recommended:
+These lifecycle methods are not essential but recommended:
 
-- [`validateThemeConfig({themeConfig, validate})`](lifecycle-apis.md#validatethemeconfigthemeconfig-validate)
-- [`validateOptions({options, validate})`](lifecycle-apis.md#validateoptionsoptions-validate)
+- [`validateThemeConfig({themeConfig, validate})`](./api/lifecycle-apis.md#validatethemeconfigthemeconfig-validate)
+- [`validateOptions({options, validate})`](./api/lifecycle-apis.md#validateoptionsoptions-validate)
 
 <!--
 
@@ -231,7 +259,7 @@ Related pieces
 ---
 
 - [Advanced Guides – Themes](using-themes.md)
-- [Lifecycle APIs](lifecycle-apis.md)
+- [Lifecycle APIs](./api/lifecycle-apis.md)
 
 References
 ---
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-analytics.md b/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-analytics.md
deleted file mode 100644
index 738c5f6e34..0000000000
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-analytics.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-id: plugin-google-analytics
-title: '📦 plugin-google-analytics'
-slug: '/api/plugins/@docusaurus/plugin-google-analytics'
----
-
-The default [Google Analytics](https://developers.google.com/analytics/devguides/collection/analyticsjs/) plugin. It is a JavaScript library for measuring how users interact with your website **in the production build**. If you are using Google Analytics 4 you might need to consider using [plugin-google-gtag](./plugin-google-gtag.md) instead.
-
-## Installation {#installation}
-
-```bash npm2yarn
-npm install --save @docusaurus/plugin-google-analytics
-```
-
-:::tip
-
-If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
-
-:::
-
-## Configuration {#configuration}
-
-```js title="docusaurus.config.js"
-module.exports = {
-  plugins: ['@docusaurus/plugin-google-analytics'],
-  themeConfig: {
-    googleAnalytics: {
-      trackingID: 'UA-141789564-1',
-      // Optional fields.
-      anonymizeIP: true, // Should IPs be anonymized?
-    },
-  },
-};
-```
diff --git a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-gtag.md b/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-gtag.md
deleted file mode 100644
index 53b760c36c..0000000000
--- a/website/versioned_docs/version-2.0.0-beta.9/api/plugins/plugin-google-gtag.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-id: plugin-google-gtag
-title: '📦 plugin-google-gtag'
-slug: '/api/plugins/@docusaurus/plugin-google-gtag'
----
-
-The default [Global Site Tag (gtag.js)](https://developers.google.com/analytics/devguides/collection/gtagjs/) plugin. It is a JavaScript tagging framework and API that allows you to send event data to Google Analytics, Google Ads, and Google Marketing Platform, **in the production build**. This section describes how to configure a Docusaurus site to enable global site tag for Google Analytics.
-
-:::tip
-
-You can use [Google's Tag Assistant](https://tagassistant.google.com/) tool to check if your gtag is set up correctly!
-
-:::
-
-## Installation {#installation}
-
-```bash npm2yarn
-npm install --save @docusaurus/plugin-google-gtag
-```
-
-:::tip
-
-If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
-
-:::
-
-## Configuration {#configuration}
-
-```js title="docusaurus.config.js"
-module.exports = {
-  plugins: ['@docusaurus/plugin-google-gtag'],
-  themeConfig: {
-    gtag: {
-      // You can also use your "G-" Measurement ID here.
-      trackingID: 'UA-141789564-1',
-      // Optional fields.
-      anonymizeIP: true, // Should IPs be anonymized?
-    },
-  },
-};
-```
diff --git a/website/versioned_docs/version-2.0.0-beta.9/deployment.mdx b/website/versioned_docs/version-2.0.0-beta.9/deployment.mdx
deleted file mode 100644
index ff492bd640..0000000000
--- a/website/versioned_docs/version-2.0.0-beta.9/deployment.mdx
+++ /dev/null
@@ -1,587 +0,0 @@
----
-id: deployment
-title: Deployment
----
-
-To build the static files of your website for production, run:
-
-```bash npm2yarn
-npm run build
-```
-
-Once it finishes, the static files will be generated within the `build` directory.
-
-:::note
-
-The only responsibility of Docusaurus is to build your site and emit static files in `build`.
-
-It is now up to you to choose how to host those static files.
-
-:::
-
-You can deploy your site to static site hosting services such as [Vercel](https://vercel.com/), [GitHub Pages](https://pages.github.com/), [Netlify](https://www.netlify.com/), [Render](https://render.com/docs/static-sites), [Surge](https://surge.sh/help/getting-started-with-surge)...
-
-A Docusaurus site is statically rendered, and it can generally work without JavaScript!
-
-## Testing your Build Locally {#testing-build-locally}
-
-It is important to test your build locally before deploying to production.
-
-Docusaurus includes a [`docusaurus serve`](cli.md#docusaurus-serve-sitedir) command for that:
-
-```bash npm2yarn
-npm run serve
-```
-
-## Trailing slash configuration {#trailing-slashes}
-
-Docusaurus has a [`trailingSlash` config](./api/docusaurus.config.js.md#trailing-slash), to allow customizing URLs/links and emitted filename patterns.
-
-The default value generally works fine.
-
-Unfortunately, each static hosting provider has a **different behavior**, and deploying the exact same site to various hosts can lead to distinct results.
-
-Depending on your host, it can be useful to change this config.
-
-:::tip
-
-Use [slorber/trailing-slash-guide](https://github.com/slorber/trailing-slash-guide) to understand better the behavior of your host and configure `trailingSlash` appropriately.
-
-:::
-
-## Self-Hosting {#self-hosting}
-
-Docusaurus can be self-hosted using [`docusaurus serve`](cli.md#docusaurus-serve-sitedir). Change port using `--port` and `--host` to change host.
-
-```bash npm2yarn
-npm run serve -- --build --port 80 --host 0.0.0.0
-```
-
-:::warning
-
-It is not the best option, compared to a static hosting provider / CDN.
-
-:::
-
-## Deploying to GitHub Pages {#deploying-to-github-pages}
-
-Docusaurus provides an easy way to publish to [GitHub Pages](https://pages.github.com/). Which is hosting that comes for free with every GitHub repository.
-
-### `docusaurus.config.js` settings {#docusaurusconfigjs-settings}
-
-First, modify your `docusaurus.config.js` and add the required params:
-
-| Name | Description |
-| --- | --- |
-| `organizationName` | The GitHub user or organization that owns the repository. If you are the owner, it is your GitHub username. In the case of Docusaurus, it is "_facebook_" which is the GitHub organization that owns Docusaurus. |
-| `projectName` | The name of the GitHub repository. For example, the repository name for Docusaurus is "docusaurus", so the project name is "docusaurus". |
-| `deploymentBranch` | The name of the branch to deploy the static files to. This defaults to "gh-pages" for non-organization GitHub Pages repos. If the repo name ends in ".github.io", you have to either specify this property or set the environment variable `DEPLOYMENT_BRANCH`. |
-| `url` | URL for your GitHub Page's user/organization page. This is commonly https://_username_.github.io. |
-| `baseUrl` | Base URL for your project. For projects hosted on GitHub pages, it follows the format "/_projectName_/". For https://github.com/facebook/docusaurus, `baseUrl` is `/docusaurus/`. |
-
-:::info
-
-In case you want to use your custom domain for GitHub Pages, create a `CNAME` file in the `static` directory. Anything within the `static` directory will be copied to the root of the `build` directory for deployment.
-
-When using a custom domain, you should be able to move back from `baseUrl: '/projectName/'` to `baseUrl: '/'`
-
-You may refer to GitHub Pages' documentation [User, Organization, and Project Pages](https://help.github.com/en/articles/user-organization-and-project-pages) for more details.
-
-:::
-
-:::caution
-
-GitHub Pages adds a trailing slash to Docusaurus URLs by default. It is recommended to set a `trailingSlash` config (`true` or `false`, not `undefined`).
-
-:::
-
-Example:
-
-```jsx {3-6} title="docusaurus.config.js"
-module.exports = {
-  // ...
-  url: 'https://endiliey.github.io', // Your website URL
-  baseUrl: '/',
-  projectName: 'endiliey.github.io',
-  organizationName: 'endiliey',
-  trailingSlash: false,
-  // ...
-};
-```
-
-:::warning
-
-By default, GitHub Pages runs published files through [Jekyll](https://jekyllrb.com/). Since Jekyll will discard any files that begin with `_`, it is recommended that you disable Jekyll by adding an empty file named `.nojekyll` file to your `static` directory.
-
-:::
-
-### Environment settings {#environment-settings}
-
-Specify the Git user as an environment variable.
-
-| Name | Description |
-| --- | --- |
-| `GIT_USER` | The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your GitHub username. The specified `GIT_USER` must have push access to the repository specified in the combination of `organizationName` and `projectName`. |
-
-Optional parameters, also set as environment variables:
-
-| Name | Description |
-| --- | --- |
-| `USE_SSH` | Set to `true` to use SSH instead of the default HTTPS for the connection to the GitHub repo. |
-| `DEPLOYMENT_BRANCH` | The branch that the website will be deployed to, defaults to `gh-pages`. For GitHub Pages Organization repos (`config.projectName` ending in `github.io`), you need to either set this env variable or specify the `deploymentBranch` param in `docusaurus.config.js`. |
-| `CURRENT_BRANCH` | The branch that contains the latest docs changes that will be deployed. Usually, the branch will be `main`, but it could be any branch (default or otherwise) except for `gh-pages`. If nothing is set for this variable, then the current branch will be used. |
-| `GIT_PASS` | Password (or token) of the `git` user (specified by `GIT_USER`). For example, to facilitate non-interactive deployment (e.g. continuous deployment) |
-
-GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment variable:
-
-| Name          | Description                                     |
-| ------------- | ----------------------------------------------- |
-| `GITHUB_HOST` | The domain name of your GitHub enterprise site. |
-| `GITHUB_PORT` | The port of your GitHub enterprise site.        |
-
-### Deploy {#deploy}
-
-Finally, to deploy your site to GitHub Pages, run:
-
-````mdx-code-block
-<Tabs>
-<TabItem value="bash" label="Bash">
-
-```bash
-GIT_USER=<GITHUB_USERNAME> yarn deploy
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows">
-
-```batch
-cmd /C "set "GIT_USER=<GITHUB_USERNAME>" && yarn deploy"
-```
-
-</TabItem>
-<TabItem value="powershell" label="PowerShell">
-
-```powershell
-cmd /C 'set "GIT_USER=<GITHUB_USERNAME>" && yarn deploy'
-```
-
-</TabItem>
-</Tabs>
-````
-
-### Triggering deployment with GitHub Actions {#triggering-deployment-with-github-actions}
-
-[GitHub Actions](https://help.github.com/en/actions) allow you to automate, customize, and execute your software development workflows right in your repository.
-
-This workflow assumes your documentation resided in `documentation` branch of your repository and your [publishing source](https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) is configured for `gh-pages` branch.
-
-1. Generate a new [SSH key](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
-1. By default, your public key should have been created in `~/.ssh/id_rsa.pub` or use the name you've provided in the previous step to add your key to [GitHub deploy keys](https://developer.github.com/v3/guides/managing-deploy-keys/).
-1. Copy key to clipboard with `xclip -sel clip < ~/.ssh/id_rsa.pub` and paste it as a [deploy key](https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys) in your repository. Copy file content if the command line doesn't work for you. Check the box for `Allow write access` before saving your deployment key.
-1. You'll need your private key as a [GitHub secret](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) to allow Docusaurus to run the deployment for you.
-1. Copy your private key with `xclip -sel clip < ~/.ssh/id_rsa` and paste a GitHub secret with name `GH_PAGES_DEPLOY`. Copy file content if the command line doesn't work for you. Save your secret.
-1. Create your [documentation workflow file](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#creating-a-workflow-file) in `.github/workflows/`. In this example it's `documentation.yml`.
-
-:::warning
-
-Please make sure that you replace `actions@github.com` with your GitHub email and `gh-actions` with your name.
-
-:::
-
-```yaml title="documentation.yml"
-name: documentation
-
-on:
-  pull_request:
-    branches: [documentation]
-  push:
-    branches: [documentation]
-
-jobs:
-  checks:
-    if: github.event_name != 'push'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v1
-      - uses: actions/setup-node@v1
-        with:
-          node-version: '12.x'
-      - name: Test Build
-        run: |
-          if [ -e yarn.lock ]; then
-            yarn install --frozen-lockfile
-          elif [ -e package-lock.json ]; then
-            npm ci
-          else
-            npm i
-          fi
-          npm run build
-  gh-release:
-    if: github.event_name != 'pull_request'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v1
-      - uses: actions/setup-node@v1
-        with:
-          node-version: '12.x'
-      - uses: webfactory/ssh-agent@v0.5.0
-        with:
-          ssh-private-key: ${{ secrets.GH_PAGES_DEPLOY }}
-      - name: Release to GitHub Pages
-        env:
-          USE_SSH: true
-          GIT_USER: git
-        run: |
-          git config --global user.email "actions@github.com"
-          git config --global user.name "gh-actions"
-          if [ -e yarn.lock ]; then
-            yarn install --frozen-lockfile
-          elif [ -e package-lock.json ]; then
-            npm ci
-          else
-            npm i
-          fi
-          npm run deploy
-```
-
-1. Now when a new pull request arrives towards your repository in branch `documentation` it will automatically ensure that Docusaurus build is successful.
-1. When pull request is merged to `documentation` branch or someone pushes to `documentation` branch directly it will be built and deployed to `gh-pages` branch.
-1. After this step, your updated documentation will be available on the GitHub pages.
-
-### Triggering deployment with Travis CI {#triggering-deployment-with-travis-ci}
-
-Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and deploying changes to your website. All you need to do to automate the deployment of your website is to invoke the `yarn deploy` script whenever your website is updated. The following section covers how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider.
-
-1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). When creating the token, grant it the `repo` scope so that it has the permissions it needs.
-1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate.
-1. Open your Travis CI dashboard. The URL looks like `https://travis-ci.com/USERNAME/REPO`, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository.
-1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username).
-1. Create a `.travis.yml` on the root of your repository with the following:
-
-```yaml title=".travis.yml"
-language: node_js
-node_js:
-  - '12.13.0'
-branches:
-  only:
-    - main
-cache:
-  yarn: true
-script:
-  - git config --global user.name "${GH_NAME}"
-  - git config --global user.email "${GH_EMAIL}"
-  - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
-  - yarn && GIT_USER="${GH_NAME}" yarn deploy
-```
-
-Now, whenever a new commit lands in `main`, Travis CI will run your suite of tests and if everything passes, your website will be deployed via the `yarn deploy` script.
-
-### Triggering deployment with Buddy {#triggering-deployment-with-buddy}
-
-[Buddy](https://buddy.works/) is an easy-to-use CI/CD tool that allows you to automate the deployment of your portal to different environments, including GitHub Pages.
-
-Follow these steps to create a pipeline that automatically deploys a new version of your website whenever you push changes to the selected branch of your project:
-
-1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). When creating the token, grant it the `repo` scope so that it has the permissions it needs.
-1. Sign in to your Buddy account and create a new project.
-1. Choose GitHub as your git hosting provider and select the repository with the code of your website.
-1. Using the left navigation panel, switch to the `Pipelines` view.
-1. Create a new pipeline. Define its name, set the trigger mode to `On push`, and select the branch that triggers the pipeline execution.
-1. Add a `Node.js` action.
-1. Add these command in the action's terminal:
-   ```bash
-   GIT_USER=<GH_PERSONAL_ACCESS_TOKEN>
-   git config --global user.email "<YOUR_GH_EMAIL>"
-   git config --global user.name "<YOUR_GH_USERNAME>"
-   yarn deploy
-   ```
-
-After creating this simple pipeline, each new commit pushed to the branch you selected deploys your website to GitHub Pages using `yarn deploy`. Read [this guide](https://buddy.works/guides/react-docusaurus) to learn more about setting up a CI/CD pipeline for Docusaurus.
-
-### Using Azure Pipelines {#using-azure-pipelines}
-
-1.  Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already.
-1.  Create an organization and within the organization create a project and connect your repository from GitHub.
-1.  Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with the `repo` scope.
-1.  In the project page (which looks like `https://dev.azure.com/ORG_NAME/REPO_NAME/_build` create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at your repository root.
-
-```yaml title="azure-pipelines.yml"
-trigger:
-  - main
-
-pool:
-  vmImage: 'ubuntu-latest'
-
-steps:
-  - checkout: self
-    persistCredentials: true
-
-  - task: NodeTool@0
-    inputs:
-      versionSpec: '10.x'
-    displayName: 'Install Node.js'
-
-  - script: |
-      git config --global user.name "${GH_NAME}"
-      git config --global user.email "${GH_EMAIL}"
-      git checkout -b main
-      echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc
-      yarn && GIT_USER="${GH_NAME}" yarn deploy
-    env:
-      GH_NAME: $(GH_NAME)
-      GH_EMAIL: $(GH_EMAIL)
-      GH_TOKEN: $(GH_TOKEN)
-    displayName: 'yarn install and build'
-```
-
-### Using Drone {#using-drone}
-
-1.  Create a new ssh key that will be the [deploy key](https://docs.github.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys#deploy-keys) for your project.
-1.  Name your private and public keys to be specific and so that it does not overwrite your other [ssh keys](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
-1.  Go to `https://github.com/USERNAME/REPO/settings/keys` and add a new deploy key by pasting in our public key you just generated.
-1.  Open your Drone.io dashboard and login. The URL looks like `https://cloud.drone.io/USERNAME/REPO`.
-1.  Click on the repository, click on activate repository, and add a secret called `git_deploy_private_key` with your private key value that you just generated.
-1.  Create a `.drone.yml` on the root of your repository with below text.
-
-```yaml
-# .drone.yml
-kind: pipeline
-type: docker
-trigger:
-  event:
-    - tag
-- name: Website
-  image: node
-  commands:
-    - mkdir -p $HOME/.ssh
-    - ssh-keyscan -t rsa github.com >> $HOME/.ssh/known_hosts
-    - echo "$GITHUB_PRIVATE_KEY" > "$HOME/.ssh/id_rsa"
-    - chmod 0600 $HOME/.ssh/id_rsa
-    - cd website
-    - npm i
-    - npm run deploy
-  environment:
-    USE_SSH: true
-    GIT_USER: $DRONE_COMMIT_AUTHOR
-    GITHUB_PRIVATE_KEY:
-      from_secret: "git_deploy_private_key"
-```
-
-Now, whenever you push a new tag to github, this trigger will start the drone ci job to publish your website.
-
-## Deploying to Netlify {#deploying-to-netlify}
-
-To deploy your Docusaurus 2 sites to [Netlify](https://www.netlify.com/), first make sure the following options are properly configured:
-
-```js {2-3} title="docusaurus.config.js"
-module.exports = {
-  url: 'https://docusaurus-2.netlify.com', // Url to your site with no trailing slash
-  baseUrl: '/', // Base directory of your site relative to your repo
-  // ...
-};
-```
-
-Then, [create your site with Netlify](https://app.netlify.com/start).
-
-While you set up the site, specify the build commands and directories as follows:
-
-- build command: `npm run build`
-- build directory: `build`
-
-If you did not configure these build options, you may still go to "Site settings" -> "Build and deploy" after your site is created.
-
-Once properly configured with the above options, your site should deploy and automatically redeploy upon merging to your deploy branch, which defaults to `main`.
-
-:::caution
-
-Some Docusaurus sites put the `docs` folder outside of `website` (most likely former Docusaurus v1 sites):
-
-```bash
-repo           # git root
-├── docs       # md files
-└── website    # docusaurus root
-```
-
-If you decide to use the `website` folder as Netlify's base directory, Netlify will not trigger builds when you update the `docs` folder, and you need to configure a [custom `ignore` command](https://docs.netlify.com/configure-builds/common-configurations/ignore-builds/):
-
-```toml title="website/netlify.toml"
-[build]
-  ignore = "git diff --quiet $CACHED_COMMIT_REF $COMMIT_REF . ../docs/"
-```
-
-:::
-
-:::warning
-
-By default, Netlify adds trailing slashes to Docusaurus URLs.
-
-It is recommended to disable the Netlify setting `Post Processing > Asset Optimization > Pretty Urls` to prevent lowercased URLs, unnecessary redirects and 404 errors.
-
-**Be very careful**: the `Disable asset optimization` global checkbox is broken and does not really disable the `Pretty URLs` setting in practice. Please make sure to **uncheck it independently**.
-
-If you want to keep the `Pretty Urls` Netlify setting on, adjust the `trailingSlash` Docusaurus config appropriately.
-
-Refer to [slorber/trailing-slash-guide](https://github.com/slorber/trailing-slash-guide) for more information.
-
-:::
-
-## Deploying to Vercel {#deploying-to-vercel}
-
-Deploying your Docusaurus project to [Vercel](https://vercel.com/) will provide you with [various benefits](https://vercel.com/) in the areas of performance and ease of use.
-
-To deploy your Docusaurus project with a [Vercel for Git Integration](https://vercel.com/docs/git-integrations), make sure it has been pushed to a Git repository.
-
-Import the project into Vercel using the [Import Flow](https://vercel.com/import/git). During the import, you will find all relevant options preconfigured for you; however, you can choose to change any of these options, a list of which can be found [here](https://vercel.com/docs/build-step#build-&-development-settings).
-
-After your project has been imported, all subsequent pushes to branches will generate [Preview Deployments](https://vercel.com/docs/platform/deployments#preview), and all changes made to the [Production Branch](https://vercel.com/docs/git-integrations#production-branch) (commonly "main") will result in a [Production Deployment](https://vercel.com/docs/platform/deployments#production).
-
-## Deploying to Render {#deploying-to-render}
-
-[Render](https://render.com) offers [free static site hosting](https://render.com/docs/static-sites) with fully managed SSL, custom domains, a global CDN and continuous auto-deploy from your Git repo. Get started in just a few minutes by following [Render's guide to deploying Docusaurus](https://render.com/docs/deploy-docusaurus).
-
-## Deploying to Qovery {#deploying-to-qovery}
-
-[Qovery](https://www.qovery.com) is a fully-managed cloud platform that runs on your AWS, Digital Ocean and Scaleway account where you can host static sites, backend APIs, databases, cron jobs, and all your other apps in one place.
-
-1. Create a Qovery account. Visit the [Qovery dashboard](https://console.qovery.com) to create an account if you don't already have one.
-
-2. Create a project
-
-- Click on **Create project** and give a name to your project.
-- Click on **Next**.
-
-3. Create a new environment
-
-- Click on **Create environment** and give a name (e.g. staging, production).
-
-4. Add an application
-
-- Click on **Create an application**, give a name and select your GitHub or GitLab repository where your Docusaurus app is located.
-- Define the main branch name and the root application path.
-- Click on **Create**.
-
-After the application is created:
-
-- Navigate to your application **Settings**
-- Select **Port**
-- Add port used by your Docusaurus application
-
-5. Deploy All you have to do now is to navigate to your application and click on **Deploy**
-
-![Deploy the app](https://hub.qovery.com/img/heroku/heroku-1.png)
-
-That's it. Watch the status and wait till the app is deployed.
-
-To open the application in your browser, click on **Action** and **Open** in your application overview
-
-## Deploying to Hostman {#deploying-to-hostman}
-
-[Hostman](https://hostman.com/) allows you to host static websites for free. Hostman automates everything, you just need to connect your repository and follow easy steps:
-
-1. Create a service
-
-To deploy a Docusaurus static website, click Create in the top-left corner of your [Dashboard](https://dashboard.hostman.com/) and choose Front-end app or static website.
-
-2. Select the project to deploy
-
-If you are logged in to Hostman with your GitHub, GitLab or Bitbucket account, at this point you will see the repository with your projects, including the private ones.
-
-Choose the project you want to deploy. It must contain the directory with the project’s files (usually it is website or my-website).
-
-To access a different repository, click Connect another repository.
-
-If you didn’t use your Git account credentials to log in, you’ll be able to access the necessary account now, and then select the project.
-
-3. Configure the build settings Next, the Website customization window will appear.
-
-Choose the Static website option from the list of frameworks.
-
-The Directory with app points at the directory that will contain the project's files after the build. You can leave it empty if during Step 2 you selected the repository with the contents of the website (or my_website) directory.
-
-The standard build command for Docusaurus will be:
-
-```bash
-yarn run build
-```
-
-You can modify the build command if needed. You can enter multiple commands separated by &&.
-
-4. Deploy Click Deploy to start the build process.
-
-Once it starts, you will enter the deployment log. If there are any issues with the code, you will get warning or error messages in the log, specifying the cause of the problem.
-
-Usually the log contains all the debugging data you'll need, but we are also here to help you solve the issues, so do not hesitate to contact us via chat.
-
-When the deployment is complete, you will receive an e-mail notification and also see a log entry.
-
-All done!
-
-Your project is up and ready.
-
-## Deploying to Surge {#deploying-to-surge}
-
-Surge is a [static web hosting platform](https://surge.sh/help/getting-started-with-surge), it is used to deploy your Docusaurus project from the command line in a minute. Deploying your project to Surge is easy and it is also free (including a custom domain and SSL).
-
-Deploy your app in a matter of seconds using surge with the following steps:
-
-1. First, install Surge using npm by running the following command:
-
-```bash
-npm install --g surge
-```
-
-2. To build the static files of your site for production in the root directory of your project, run:
-
-```bash
-npm run build
-```
-
-3. Then, run this command inside the root directory of your project:
-
-```bash
-surge build/
-```
-
-First-time users of Surge would be prompted to create an account from the command line(happens only once).
-
-Confirm that the site you want to publish is in the `build` directory, a randomly generated subdomain `*.surge.sh subdomain` is always given (which can be edited).
-
-### Using your domain {#using-your-domain}
-
-If you have a domain name you can deploy your site using surge to your domain using the command:
-
-```bash
-surge build/ yourdomain.com
-```
-
-Your site is now deployed for free at `subdomain.surge.sh` or `yourdomain.com` depending on the method you chose.
-
-### Setting up CNAME file {#setting-up-cname-file}
-
-Store your domain in a CNAME file for future deployments with the following command:
-
-```bash
-echo subdomain.surge.sh > CNAME
-```
-
-You can deploy any other changes in the future with the command `surge`.
-
-## Deploying to QuantCDN {#deploying-to-quantcdn}
-
-1. Install [Quant CLI](https://docs.quantcdn.io/docs/cli/get-started)
-
-2. Create a QuantCDN account by [signing up](https://dashboard.quantcdn.io/register)
-
-3. Initialize your project with `quant init` and fill in your credentials:
-
-```bash
-quant init
-```
-
-4. Deploy your site
-
-```bash
-quant deploy
-```
-
-See [docs](https://docs.quantcdn.io/docs/cli/continuous-integration) and [blog](https://www.quantcdn.io/blog) for more examples and use cases for deploying to QuantCDN.
diff --git a/website/versioned_sidebars/version-2.0.0-beta.11-sidebars.json b/website/versioned_sidebars/version-2.0.0-beta.11-sidebars.json
new file mode 100644
index 0000000000..69f1c69c4f
--- /dev/null
+++ b/website/versioned_sidebars/version-2.0.0-beta.11-sidebars.json
@@ -0,0 +1,122 @@
+{
+  "docs": [
+    "introduction",
+    {
+      "type": "category",
+      "label": "Getting Started",
+      "link": {
+        "type": "generated-index"
+      },
+      "collapsed": false,
+      "items": [
+        "installation",
+        "configuration",
+        "playground",
+        "typescript-support"
+      ]
+    },
+    {
+      "type": "category",
+      "label": "Guides",
+      "link": {
+        "type": "generated-index",
+        "title": "Docusaurus Guides",
+        "description": "Let's learn about the most important Docusaurus concepts!"
+      },
+      "items": [
+        "guides/creating-pages",
+        {
+          "type": "category",
+          "label": "Docs",
+          "link": {
+            "type": "doc",
+            "id": "guides/docs/introduction"
+          },
+          "items": [
+            "guides/docs/create-doc",
+            "guides/docs/sidebar",
+            "guides/docs/versioning",
+            "guides/docs/markdown-features",
+            "guides/docs/multi-instance"
+          ]
+        },
+        "blog",
+        {
+          "type": "category",
+          "label": "Markdown Features",
+          "link": {
+            "type": "doc",
+            "id": "guides/markdown-features/introduction"
+          },
+          "items": [
+            "guides/markdown-features/react",
+            "guides/markdown-features/tabs",
+            "guides/markdown-features/code-blocks",
+            "guides/markdown-features/admonitions",
+            "guides/markdown-features/headings",
+            "guides/markdown-features/inline-toc",
+            "guides/markdown-features/assets",
+            "guides/markdown-features/plugins",
+            "guides/markdown-features/math-equations",
+            "guides/markdown-features/head-metadata"
+          ]
+        },
+        "styling-layout",
+        "static-assets",
+        "search",
+        "browser-support",
+        "seo",
+        "deployment",
+        {
+          "type": "category",
+          "label": "Internationalization",
+          "link": {
+            "type": "doc",
+            "id": "i18n/introduction"
+          },
+          "items": [
+            {
+              "type": "doc",
+              "id": "i18n/tutorial",
+              "label": "Tutorial"
+            },
+            {
+              "type": "doc",
+              "id": "i18n/git",
+              "label": "Using Git"
+            },
+            {
+              "type": "doc",
+              "id": "i18n/crowdin",
+              "label": "Using Crowdin"
+            }
+          ]
+        }
+      ]
+    },
+    {
+      "type": "category",
+      "label": "Advanced Guides",
+      "items": ["using-plugins", "using-themes", "presets"]
+    },
+    {
+      "type": "category",
+      "label": "Migrating from v1 to v2",
+      "items": [
+        "migration/migration-overview",
+        "migration/migration-automated",
+        "migration/migration-manual",
+        "migration/migration-versioned-sites",
+        "migration/migration-translated-sites"
+      ]
+    }
+  ],
+  "api": [
+    "cli",
+    "docusaurus-core",
+    {
+      "type": "autogenerated",
+      "dirName": "api"
+    }
+  ]
+}
diff --git a/website/versioned_sidebars/version-2.0.0-beta.9-sidebars.json b/website/versioned_sidebars/version-2.0.0-beta.9-sidebars.json
deleted file mode 100644
index da6673fa19..0000000000
--- a/website/versioned_sidebars/version-2.0.0-beta.9-sidebars.json
+++ /dev/null
@@ -1,322 +0,0 @@
-{
-  "VersionedSideBarNameDoesNotMatter/docs": [
-    {
-      "type": "doc",
-      "id": "version-2.0.0-beta.9/introduction"
-    },
-    {
-      "type": "category",
-      "label": "Getting Started",
-      "collapsed": false,
-      "items": [
-        {
-          "type": "doc",
-          "id": "version-2.0.0-beta.9/installation"
-        },
-        {
-          "type": "doc",
-          "id": "version-2.0.0-beta.9/configuration"
-        },
-        {
-          "type": "doc",
-          "id": "version-2.0.0-beta.9/playground"
-        },
-        {
-          "type": "doc",
-          "id": "version-2.0.0-beta.9/typescript-support"
-        }
-      ],
-      "collapsible": true
-    },
-    {
-      "type": "category",
-      "label": "Guides",
-      "items": [
-        {
-          "type": "doc",
-          "id": "guides/creating-pages"
-        },
-        {
-          "type": "category",
-          "collapsed": true,
-          "collapsible": true,
-          "label": "Docs",
-          "items": [
-            {
-              "type": "doc",
-              "id": "guides/docs/introduction"
-            },
-            {
-              "type": "doc",
-              "id": "guides/docs/create-doc"
-            },
-            {
-              "type": "doc",
-              "id": "guides/docs/sidebar"
-            },
-            {
-              "type": "doc",
-              "id": "guides/docs/versioning"
-            },
-            {
-              "type": "doc",
-              "id": "guides/docs/markdown-features"
-            },
-            {
-              "type": "doc",
-              "id": "guides/docs/multi-instance"
-            }
-          ]
-        },
-        {
-          "type": "doc",
-          "id": "blog"
-        },
-        {
-          "type": "category",
-          "label": "Markdown Features",
-          "items": [
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/introduction"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/react"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/tabs"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/code-blocks"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/admonitions"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/headings"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/inline-toc"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/assets"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/plugins"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/math-equations"
-            },
-            {
-              "type": "doc",
-              "id": "guides/markdown-features/head-metadatas"
-            }
-          ],
-          "collapsible": true,
-          "collapsed": true
-        },
-        {
-          "type": "doc",
-          "id": "styling-layout"
-        },
-        {
-          "type": "doc",
-          "id": "static-assets"
-        },
-        {
-          "type": "doc",
-          "id": "search"
-        },
-        {
-          "type": "doc",
-          "id": "browser-support"
-        },
-        {
-          "type": "doc",
-          "id": "deployment"
-        },
-        {
-          "type": "category",
-          "label": "Internationalization",
-          "items": [
-            {
-              "type": "doc",
-              "id": "i18n/introduction"
-            },
-            {
-              "type": "doc",
-              "id": "i18n/tutorial"
-            },
-            {
-              "type": "doc",
-              "id": "i18n/git"
-            },
-            {
-              "type": "doc",
-              "id": "i18n/crowdin"
-            }
-          ],
-          "collapsible": true,
-          "collapsed": true
-        }
-      ],
-      "collapsible": true,
-      "collapsed": true
-    },
-    {
-      "type": "category",
-      "label": "Advanced Guides",
-      "items": [
-        {
-          "type": "doc",
-          "id": "using-plugins"
-        },
-        {
-          "type": "doc",
-          "id": "using-themes"
-        },
-        {
-          "type": "doc",
-          "id": "presets"
-        }
-      ],
-      "collapsible": true,
-      "collapsed": true
-    },
-    {
-      "type": "category",
-      "label": "Migrating from v1 to v2",
-      "items": [
-        {
-          "type": "doc",
-          "id": "migration/migration-overview"
-        },
-        {
-          "type": "doc",
-          "id": "migration/migration-automated"
-        },
-        {
-          "type": "doc",
-          "id": "migration/migration-manual"
-        },
-        {
-          "type": "doc",
-          "id": "migration/migration-versioned-sites"
-        },
-        {
-          "type": "doc",
-          "id": "migration/migration-translated-sites"
-        }
-      ],
-      "collapsible": true,
-      "collapsed": true
-    }
-  ],
-  "api": [
-    {
-      "type": "doc",
-      "id": "cli"
-    },
-    {
-      "type": "doc",
-      "id": "docusaurus-core"
-    },
-    {
-      "type": "doc",
-      "id": "api/docusaurus.config.js"
-    },
-    {
-      "type": "doc",
-      "id": "lifecycle-apis"
-    },
-    {
-      "type": "category",
-      "label": "Plugins",
-      "items": [
-        {
-          "type": "doc",
-          "id": "api/plugins/plugins-overview"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-content-docs"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-content-blog"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-content-pages"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-client-redirects"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-debug"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-google-analytics"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-google-gtag"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-ideal-image"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-pwa"
-        },
-        {
-          "type": "doc",
-          "id": "api/plugins/plugin-sitemap"
-        }
-      ],
-      "collapsible": true,
-      "collapsed": true
-    },
-    {
-      "type": "category",
-      "label": "Themes",
-      "items": [
-        {
-          "type": "doc",
-          "id": "api/themes/themes-overview"
-        },
-        {
-          "type": "doc",
-          "id": "api/themes/theme-configuration"
-        },
-        {
-          "type": "doc",
-          "id": "api/themes/theme-classic"
-        },
-        {
-          "type": "doc",
-          "id": "api/themes/theme-live-codeblock"
-        },
-        {
-          "type": "doc",
-          "id": "api/themes/theme-search-algolia"
-        }
-      ],
-      "collapsible": true,
-      "collapsed": true
-    }
-  ]
-}
diff --git a/website/versions.json b/website/versions.json
index a5cfb0e849..c466e69ee1 100644
--- a/website/versions.json
+++ b/website/versions.json
@@ -1 +1 @@
-["2.0.0-beta.10", "2.0.0-beta.9"]
+["2.0.0-beta.11", "2.0.0-beta.10"]
diff --git a/website/versionsArchived.json b/website/versionsArchived.json
index 67f6d1e597..72e5423feb 100644
--- a/website/versionsArchived.json
+++ b/website/versionsArchived.json
@@ -1,4 +1,5 @@
 {
+  "2.0.0-beta.9": "https://61b203d85554724fcf8487a7--docusaurus-2.netlify.app/docs/2.0.0-beta.9",
   "2.0.0-beta.8": "https://61b0f073d92903000adc8dae--docusaurus-2.netlify.app/docs/2.0.0-beta.8",
   "2.0.0-beta.7": "https://6180b81acd61ea000825bc41--docusaurus-2.netlify.app/docs/2.0.0-beta.7",
   "2.0.0-beta.6": "https://61716a75858b7d0007e84c89--docusaurus-2.netlify.app/docs/2.0.0-beta.6",