docs(website): use .mdx extension for every docs (#8490)

website/versioned_docs/version-2.0.1/api/docusaurus.config.js.mdx

@@ -119,7 +119,7 @@ Refer to the [deployment guide](../deployment.mdx) and [slorber/trailing-slash-g
 
 - Type: `Object`
 
-The i18n configuration object to [localize your site](../i18n/i18n-introduction.md).
+The i18n configuration object to [localize your site](../i18n/i18n-introduction.mdx).
 
 Example:
 
@@ -201,7 +201,7 @@ By default, it prints a warning, to let you know about your broken Markdown link
 
 - Type: `'ignore' | 'log' | 'warn' | 'throw'`
 
-The behavior of Docusaurus when it detects any [duplicate routes](/guides/creating-pages.md#duplicate-routes).
+The behavior of Docusaurus when it detects any [duplicate routes](/guides/creating-pages.mdx#duplicate-routes).
 
 By default, it displays a warning after you run `yarn start` or `yarn build`.
 
@@ -283,7 +283,7 @@ module.exports = {
 
 - Type: `Object`
 
-The [theme configuration](./themes/theme-configuration.md) object to customize your site UI like navbar and footer.
+The [theme configuration](./themes/theme-configuration.mdx) object to customize your site UI like navbar and footer.
 
 Example:
 
@@ -354,7 +354,7 @@ module.exports = {
 type PluginConfig = string | [string, any] | PluginModule | [PluginModule, any];
 ```
 
-See [plugin method references](./plugin-methods/README.md) for the shape of a `PluginModule`.
+See [plugin method references](./plugin-methods/README.mdx) for the shape of a `PluginModule`.
 
 ```js title="docusaurus.config.js"
 module.exports = {
@@ -482,7 +482,7 @@ By default, the `<link>` tags will have `rel="stylesheet"`, but you can explicit
 
 ### `clientModules` {#clientModules}
 
-An array of [client modules](../advanced/client.md#client-modules) to load globally on your site.
+An array of [client modules](../advanced/client.mdx#client-modules) to load globally on your site.
 
 Example:
 

website/versioned_docs/version-2.0.1/api/misc/eslint-plugin/README.mdx

@@ -51,8 +51,8 @@ Each config contains a set of rules. For more fine-grained control, you can also
 
 | Name | Description |  |
 | --- | --- | --- |
-| [`@docusaurus/no-untranslated-text`](./no-untranslated-text.md) | Enforce text labels in JSX to be wrapped by translate calls |  |
-| [`@docusaurus/string-literal-i18n-messages`](./string-literal-i18n-messages.md) | Enforce translate APIs to be called on plain text labels | ✅ |
+| [`@docusaurus/no-untranslated-text`](./no-untranslated-text.mdx) | Enforce text labels in JSX to be wrapped by translate calls |  |
+| [`@docusaurus/string-literal-i18n-messages`](./string-literal-i18n-messages.mdx) | Enforce translate APIs to be called on plain text labels | ✅ |
 
 ✅ = recommended
 

website/versioned_docs/version-2.0.1/api/misc/eslint-plugin/no-untranslated-text.mdx

@@ -8,7 +8,7 @@ import APITable from '@site/src/components/APITable';
 
 Enforce text labels in JSX to be wrapped by translate calls.
 
-When the [i18n feature](../../../i18n/i18n-introduction.md) is used, this rule ensures that all labels appearing on the website are translatable, so no string accidentally slips through untranslated.
+When the [i18n feature](../../../i18n/i18n-introduction.mdx) is used, this rule ensures that all labels appearing on the website are translatable, so no string accidentally slips through untranslated.
 
 ## Rule Details {#details}
 
@@ -46,7 +46,7 @@ Accepted fields:
 
 ## When Not To Use It {#when-not-to-use}
 
-If you're not using the [i18n feature](../../../i18n/i18n-introduction.md), you can disable this rule. You can also disable this rule where the text is not supposed to be translated.
+If you're not using the [i18n feature](../../../i18n/i18n-introduction.mdx), you can disable this rule. You can also disable this rule where the text is not supposed to be translated.
 
 ## Further Reading {#further-reading}
 

website/versioned_docs/version-2.0.1/api/misc/eslint-plugin/string-literal-i18n-messages.mdx

@@ -6,7 +6,7 @@ slug: /api/misc/@docusaurus/eslint-plugin/string-literal-i18n-messages
 
 Enforce translate APIs to be called on plain text labels.
 
-Docusaurus offers the [`docusaurus write-translations`](../../../cli.md#docusaurus-write-translations-sitedir) API, which statically extracts the text labels marked as translatable. Dynamic values used in `<Translate>` or `translate()` calls will fail to be extracted. This rule will ensure that all translate calls are statically extractable.
+Docusaurus offers the [`docusaurus write-translations`](../../../cli.mdx#docusaurus-write-translations-sitedir) API, which statically extracts the text labels marked as translatable. Dynamic values used in `<Translate>` or `translate()` calls will fail to be extracted. This rule will ensure that all translate calls are statically extractable.
 
 ## Rule Details {#details}
 
@@ -42,7 +42,7 @@ translate({message: 'The logo of site {siteName}'}, {siteName: 'Docusaurus'})
 
 ## When Not To Use It {#when-not-to-use}
 
-If you're not using the [i18n feature](../../../i18n/i18n-introduction.md), you can disable this rule.
+If you're not using the [i18n feature](../../../i18n/i18n-introduction.mdx), you can disable this rule.
 
 ## Further Reading {#further-reading}
 

website/versioned_docs/version-2.0.1/api/plugin-methods/README.mdx

@@ -13,7 +13,7 @@ Plugin APIs are shared by themes and plugins—themes are loaded just like plugi
 Every plugin is imported as a module. The module is expected to have the following members:
 
 - A **default export**: the constructor function for the plugin.
-- **Named exports**: the [static methods](./static-methods.md) called before plugins are initialized.
+- **Named exports**: the [static methods](./static-methods.mdx) called before plugins are initialized.
 
 ## Plugin constructor {#plugin-constructor}
 
@@ -35,7 +35,7 @@ type LoadContext = {
 
 ### `options` {#options}
 
-`options` are the [second optional parameter when the plugins are used](../../using-plugins.md#configuring-plugins). `options` are plugin-specific and are specified by users when they use them in `docusaurus.config.js`. If there's a [`validateOptions`](./static-methods.md#validateOptions) function exported, the `options` will be validated and normalized beforehand.
+`options` are the [second optional parameter when the plugins are used](../../using-plugins.mdx#configuring-plugins). `options` are plugin-specific and are specified by users when they use them in `docusaurus.config.js`. If there's a [`validateOptions`](./static-methods.mdx#validateOptions) function exported, the `options` will be validated and normalized beforehand.
 
 Alternatively, if a preset contains the plugin, the preset will then be in charge of passing the correct options into the plugin. It is up to the individual plugin to define what options it takes.
 

website/versioned_docs/version-2.0.1/api/plugin-methods/i18n-lifecycles.mdx

@@ -15,7 +15,7 @@ Returns translation files `{path: string, content: ChromeI18nJSON}`:
 - `path`: relative to the plugin localized folder `i18n/[locale]/[pluginName]`. Extension `.json` should be omitted to remain generic.
 - `content`: using the Chrome i18n JSON format.
 
-These files will be written by the [`write-translations` CLI](../../cli.md#docusaurus-write-translations-sitedir) to the plugin i18n subfolder, and will be read in the appropriate locale before calling [`translateContent()`](#translateContent) and [`translateThemeConfig()`](#translateThemeConfig)
+These files will be written by the [`write-translations` CLI](../../cli.mdx#docusaurus-write-translations-sitedir) to the plugin i18n subfolder, and will be read in the appropriate locale before calling [`translateContent()`](#translateContent) and [`translateThemeConfig()`](#translateThemeConfig)
 
 Example:
 

website/versioned_docs/version-2.0.1/api/plugin-methods/lifecycle-apis.mdx

@@ -111,7 +111,7 @@ export default function friendsPlugin(context, options) {
 
 This function permits one to create some global plugin data that can be read from any page, including the pages created by other plugins, and your theme layout.
 
-This data becomes accessible to your client-side/theme code through the [`useGlobalData`](../../docusaurus-core.md#useGlobalData) and [`usePluginData`](../../docusaurus-core.md#usePluginData) hooks.
+This data becomes accessible to your client-side/theme code through the [`useGlobalData`](../../docusaurus-core.mdx#useGlobalData) and [`usePluginData`](../../docusaurus-core.mdx#usePluginData) hooks.
 
 :::caution
 
@@ -399,7 +399,7 @@ module.exports = function (context, options) {
 
 ## `getClientModules()` {#getClientModules}
 
-Returns an array of paths to the [client modules](../../advanced/client.md#client-modules) that are to be imported into the client bundle.
+Returns an array of paths to the [client modules](../../advanced/client.mdx#client-modules) that are to be imported into the client bundle.
 
 As an example, to make your theme load a `customCss` or `customJs` file path from `options` passed in by the user:
 

website/versioned_docs/version-2.0.1/api/plugins/overview.mdx

@@ -13,18 +13,18 @@ We provide official Docusaurus plugins.
 
 These plugins are responsible for loading your site's content, and creating pages for your theme to render.
 
-- [@docusaurus/plugin-content-docs](./plugin-content-docs.md)
-- [@docusaurus/plugin-content-blog](./plugin-content-blog.md)
-- [@docusaurus/plugin-content-pages](./plugin-content-pages.md)
+- [@docusaurus/plugin-content-docs](./plugin-content-docs.mdx)
+- [@docusaurus/plugin-content-blog](./plugin-content-blog.mdx)
+- [@docusaurus/plugin-content-pages](./plugin-content-pages.mdx)
 
 ## Behavior plugins {#behavior-plugins}
 
 These plugins will add a useful behavior to your Docusaurus site.
 
-- [@docusaurus/plugin-debug](./plugin-debug.md)
-- [@docusaurus/plugin-sitemap](./plugin-sitemap.md)
-- [@docusaurus/plugin-pwa](./plugin-pwa.md)
-- [@docusaurus/plugin-client-redirects](./plugin-client-redirects.md)
-- [@docusaurus/plugin-ideal-image](./plugin-ideal-image.md)
-- [@docusaurus/plugin-google-analytics](./plugin-google-analytics.md)
-- [@docusaurus/plugin-google-gtag](./plugin-google-gtag.md)
+- [@docusaurus/plugin-debug](./plugin-debug.mdx)
+- [@docusaurus/plugin-sitemap](./plugin-sitemap.mdx)
+- [@docusaurus/plugin-pwa](./plugin-pwa.mdx)
+- [@docusaurus/plugin-client-redirects](./plugin-client-redirects.mdx)
+- [@docusaurus/plugin-ideal-image](./plugin-ideal-image.mdx)
+- [@docusaurus/plugin-google-analytics](./plugin-google-analytics.mdx)
+- [@docusaurus/plugin-google-gtag](./plugin-google-gtag.mdx)

website/versioned_docs/version-2.0.1/api/plugins/plugin-client-redirects.mdx

@@ -52,7 +52,7 @@ Accepted fields:
 
 :::note
 
-This plugin will also read the [`siteConfig.onDuplicateRoutes`](../docusaurus.config.js.md#onDuplicateRoutes) config to adjust its logging level when multiple files will be emitted to the same location.
+This plugin will also read the [`siteConfig.onDuplicateRoutes`](../docusaurus.config.js.mdx#onDuplicateRoutes) config to adjust its logging level when multiple files will be emitted to the same location.
 
 :::
 

website/versioned_docs/version-2.0.1/api/plugins/plugin-content-blog.mdx

@@ -246,13 +246,13 @@ A Markdown blog post
 
 ## i18n {#i18n}
 
-Read the [i18n introduction](../../i18n/i18n-introduction.md) first.
+Read the [i18n introduction](../../i18n/i18n-introduction.mdx) first.
 
 ### Translation files location {#translation-files-location}
 
 - **Base path**: `website/i18n/[locale]/docusaurus-plugin-content-blog`
 - **Multi-instance path**: `website/i18n/[locale]/docusaurus-plugin-content-blog-[pluginId]`
-- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations-sitedir)
+- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.mdx#docusaurus-write-translations-sitedir)
 - **Markdown files**: `website/i18n/[locale]/docusaurus-plugin-content-blog`
 
 ### Example file-system structure {#example-file-system-structure}

website/versioned_docs/version-2.0.1/api/plugins/plugin-content-docs.mdx

@@ -7,7 +7,7 @@ slug: /api/plugins/@docusaurus/plugin-content-docs
 
 import APITable from '@site/src/components/APITable';
 
-Provides the [Docs](../../guides/docs/docs-introduction.md) functionality and is the default docs plugin for Docusaurus.
+Provides the [Docs](../../guides/docs/docs-introduction.mdx) functionality and is the default docs plugin for Docusaurus.
 
 ## Installation {#installation}
 
@@ -274,7 +274,7 @@ Accepted fields:
 | `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. |
 | `sidebar_custom_props` | `string` | `undefined` | Assign custom metadata to the sidebar item referencing this doc. |
-| `displayed_sidebar` | `string` | `undefined` | Force the display of a given sidebar when browsing the current document. Read the [multiple sidebars guide](../../guides/docs/sidebar/multiple-sidebars.md) for details. |
+| `displayed_sidebar` | `string` | `undefined` | Force the display of a given sidebar when browsing the current document. Read the [multiple sidebars guide](../../guides/docs/sidebar/multiple-sidebars.mdx) for details. |
 | `hide_title` | `boolean` | `false` | Whether to hide the title at the top of the doc. It only hides a title declared through the front matter, 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. |
 | `toc_min_heading_level` | `number` | `2` | The minimum heading level shown in the table of contents. Must be between 2 and 6 and lower or equal to the max value. |
@@ -333,13 +333,13 @@ My Document Markdown content
 
 ## i18n {#i18n}
 
-Read the [i18n introduction](../../i18n/i18n-introduction.md) first.
+Read the [i18n introduction](../../i18n/i18n-introduction.mdx) first.
 
 ### Translation files location {#translation-files-location}
 
 - **Base path**: `website/i18n/[locale]/docusaurus-plugin-content-docs`
 - **Multi-instance path**: `website/i18n/[locale]/docusaurus-plugin-content-docs-[pluginId]`
-- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations-sitedir)
+- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.mdx#docusaurus-write-translations-sitedir)
 - **Markdown files**: `website/i18n/[locale]/docusaurus-plugin-content-docs/[versionName]`
 
 ### Example file-system structure {#example-file-system-structure}

website/versioned_docs/version-2.0.1/api/plugins/plugin-content-pages.mdx

@@ -7,7 +7,7 @@ slug: /api/plugins/@docusaurus/plugin-content-pages
 
 import APITable from '@site/src/components/APITable';
 
-The default pages plugin for Docusaurus. The classic template ships with this plugin with default configurations. This plugin provides [creating pages](guides/creating-pages.md) functionality.
+The default pages plugin for Docusaurus. The classic template ships with this plugin with default configurations. This plugin provides [creating pages](guides/creating-pages.mdx) functionality.
 
 ## Installation {#installation}
 
@@ -81,13 +81,13 @@ const config = {
 
 ## i18n {#i18n}
 
-Read the [i18n introduction](../../i18n/i18n-introduction.md) first.
+Read the [i18n introduction](../../i18n/i18n-introduction.mdx) first.
 
 ### Translation files location {#translation-files-location}
 
 - **Base path**: `website/i18n/[locale]/docusaurus-plugin-content-pages`
 - **Multi-instance path**: `website/i18n/[locale]/docusaurus-plugin-content-pages-[pluginId]`
-- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations-sitedir)
+- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.mdx#docusaurus-write-translations-sitedir)
 - **Markdown files**: `website/i18n/[locale]/docusaurus-plugin-content-pages`
 
 ### Example file-system structure {#example-file-system-structure}

website/versioned_docs/version-2.0.1/api/plugins/plugin-debug.mdx

@@ -72,7 +72,7 @@ Most Docusaurus users configure this plugin through the preset options.
 <TabItem value="preset" label="Preset options">
 ```
 
-If you use a preset, configure this plugin through the [preset options](../../using-plugins.md#docusauruspreset-classic):
+If you use a preset, configure this plugin through the [preset options](../../using-plugins.mdx#docusauruspreset-classic):
 
 ```js title="docusaurus.config.js"
 module.exports = {

website/versioned_docs/version-2.0.1/api/plugins/plugin-google-analytics.mdx

@@ -7,7 +7,7 @@ slug: /api/plugins/@docusaurus/plugin-google-analytics
 
 import APITable from '@site/src/components/APITable';
 
-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.
+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.mdx) instead.
 
 :::caution production only
 

website/versioned_docs/version-2.0.1/api/plugins/plugin-pwa.mdx

@@ -294,7 +294,7 @@ import CodeBlock from '@theme/CodeBlock';
 
 ## Customizing reload popup {#customizing-reload-popup}
 
-The `@theme/PwaReloadPopup` component is rendered when a new service worker is waiting to be installed, and we suggest a reload to the user. You can [swizzle](../../swizzling.md) this component and implement your own UI. It will receive an `onReload` callback as props, which should be called when the `reload` button is clicked. This will tell the service worker to install the waiting service worker and reload the page.
+The `@theme/PwaReloadPopup` component is rendered when a new service worker is waiting to be installed, and we suggest a reload to the user. You can [swizzle](../../swizzling.mdx) this component and implement your own UI. It will receive an `onReload` callback as props, which should be called when the `reload` button is clicked. This will tell the service worker to install the waiting service worker and reload the page.
 
 The default theme includes an implementation for the reload popup and uses [Infima Alerts](https://infima.dev/docs/components/alert).
 

website/versioned_docs/version-2.0.1/api/plugins/plugin-sitemap.mdx

@@ -52,8 +52,8 @@ Accepted fields:
 
 This plugin also respects some site config:
 
-- [`noIndex`](../docusaurus.config.js.md#noIndex): results in no sitemap generated
-- [`trailingSlash`](../docusaurus.config.js.md#trailingSlash): determines if the URLs in the sitemap have trailing slashes
+- [`noIndex`](../docusaurus.config.js.mdx#noIndex): results in no sitemap generated
+- [`trailingSlash`](../docusaurus.config.js.mdx#trailingSlash): determines if the URLs in the sitemap have trailing slashes
 
 :::
 

website/versioned_docs/version-2.0.1/api/themes/overview.mdx

@@ -11,9 +11,9 @@ We provide official Docusaurus themes.
 
 ## Main themes {#main-themes}
 
-The main themes implement the user interface for the [docs](../plugins/plugin-content-docs.md), [blog](../plugins/plugin-content-blog.md) and [pages](../plugins/plugin-content-pages.md) plugins.
+The main themes implement the user interface for the [docs](../plugins/plugin-content-docs.mdx), [blog](../plugins/plugin-content-blog.mdx) and [pages](../plugins/plugin-content-pages.mdx) plugins.
 
-- [@docusaurus/theme-classic](./theme-classic.md)
+- [@docusaurus/theme-classic](./theme-classic.mdx)
 - 🚧 other themes are planned
 
 :::caution
@@ -30,5 +30,5 @@ We are not there yet: only the classic theme is production ready.
 
 These themes will enhance the existing main themes with additional user-interface related features.
 
-- [@docusaurus/theme-live-codeblock](./theme-live-codeblock.md)
-- [@docusaurus/theme-search-algolia](./theme-search-algolia.md)
+- [@docusaurus/theme-live-codeblock](./theme-live-codeblock.mdx)
+- [@docusaurus/theme-search-algolia](./theme-search-algolia.mdx)

website/versioned_docs/version-2.0.1/api/themes/theme-classic.mdx

@@ -7,7 +7,7 @@ slug: /api/themes/@docusaurus/theme-classic
 
 The classic theme for Docusaurus.
 
-You can refer to the [theme configuration page](theme-configuration.md) for more details on the configuration.
+You can refer to the [theme configuration page](theme-configuration.mdx) for more details on the configuration.
 
 ```bash npm2yarn
 npm install --save @docusaurus/theme-classic
@@ -29,7 +29,7 @@ Accepted fields:
 
 | Option | Type | Default | Description |
 | --- | --- | --- | --- |
-| `customCss` | <code>string[] \| string</code> | `[]` | Stylesheets to be imported globally as [client modules](../../advanced/client.md#client-modules). Relative paths are resolved against the site directory. |
+| `customCss` | <code>string[] \| string</code> | `[]` | Stylesheets to be imported globally as [client modules](../../advanced/client.mdx#client-modules). Relative paths are resolved against the site directory. |
 
 ```mdx-code-block
 </APITable>
@@ -37,7 +37,7 @@ Accepted fields:
 
 :::note
 
-Most configuration for the theme is done in `themeConfig`, which can be found in [theme configuration](./theme-configuration.md).
+Most configuration for the theme is done in `themeConfig`, which can be found in [theme configuration](./theme-configuration.mdx).
 
 :::
 

website/versioned_docs/version-2.0.1/api/themes/theme-configuration.mdx

@@ -9,7 +9,7 @@ toc_max_heading_level: 4
 
 import APITable from '@site/src/components/APITable';
 
-This configuration applies to all [main themes](./overview.md).
+This configuration applies to all [main themes](./overview.mdx).
 
 ## Common {#common}
 
@@ -180,7 +180,7 @@ Accepted fields:
 
 ### Navbar logo {#navbar-logo}
 
-The logo can be placed in [static folder](static-assets.md). Logo URL is set to base URL of your site by default. Although you can specify your own URL for the logo, if it is an external link, it will open in a new tab. In addition, you can override a value for the target attribute of logo link, it can come in handy if you are hosting docs website in a subdirectory of your main website, and in which case you probably do not need a link in the logo to the main website will open in a new tab.
+The logo can be placed in [static folder](static-assets.mdx). Logo URL is set to base URL of your site by default. Although you can specify your own URL for the logo, if it is an external link, it will open in a new tab. In addition, you can override a value for the target attribute of logo link, it can come in handy if you are hosting docs website in a subdirectory of your main website, and in which case you probably do not need a link in the logo to the main website will open in a new tab.
 
 To improve dark mode support, you can also set a different logo for this mode.
 
@@ -600,7 +600,7 @@ module.exports = {
 
 #### Navbar locale dropdown {#navbar-locale-dropdown}
 
-If you use the [i18n feature](../../i18n/i18n-introduction.md), this special navbar item type will render a dropdown with all your site's available locales.
+If you use the [i18n feature](../../i18n/i18n-introduction.mdx), this special navbar item type will render a dropdown with all your site's available locales.
 
 The user will be able to switch from one locale to another, while staying on the same page.
 
@@ -648,7 +648,7 @@ module.exports = {
 
 #### Navbar search {#navbar-search}
 
-If you use the [search](../../search.md), the search bar will be the rightmost element in the navbar.
+If you use the [search](../../search.mdx), the search bar will be the rightmost element in the navbar.
 
 However, with this special navbar item type, you can change the default location.
 
@@ -835,7 +835,7 @@ module.exports = {
 
 ## Footer {#footer-1}
 
-You can add logo and a copyright to the footer via `themeConfig.footer`. Logo can be placed in [static folder](static-assets.md). Logo URL works in the same way of the navbar logo.
+You can add logo and a copyright to the footer via `themeConfig.footer`. Logo can be placed in [static folder](static-assets.mdx). Logo URL works in the same way of the navbar logo.
 
 Accepted fields:
 
@@ -1066,13 +1066,13 @@ function ExamplePage() {
 
 ## i18n {#i18n}
 
-Read the [i18n introduction](../../i18n/i18n-introduction.md) first.
+Read the [i18n introduction](../../i18n/i18n-introduction.mdx) first.
 
 ### Translation files location {#translation-files-location}
 
 - **Base path**: `website/i18n/[locale]/docusaurus-theme-[themeName]`
 - **Multi-instance path**: N/A
-- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations-sitedir)
+- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.mdx#docusaurus-write-translations-sitedir)
 - **Markdown files**: N/A
 
 ### Example file-system structure {#example-file-system-structure}

website/versioned_docs/version-2.0.1/api/themes/theme-search-algolia.mdx

@@ -5,7 +5,7 @@ slug: /api/themes/@docusaurus/theme-search-algolia
 
 # 📦 theme-search-algolia
 
-This theme provides a `@theme/SearchBar` component that integrates with Algolia DocSearch easily. Combined with `@docusaurus/theme-classic`, it provides a very easy search integration. You can read more on [search](../../search.md) documentation.
+This theme provides a `@theme/SearchBar` component that integrates with Algolia DocSearch easily. Combined with `@docusaurus/theme-classic`, it provides a very easy search integration. You can read more on [search](../../search.mdx) documentation.
 
 ```bash npm2yarn
 npm install --save @docusaurus/theme-search-algolia