Before participating in Docusaurus' communities, [please read our Code of Conduct](https://engineering.fb.com/codeofconduct/). We have adopted the [Contributor Covenant](https://www.contributor-covenant.org/) and we expect that all community members adhere to the guidelines within.

Stack Overflow is a popular forum to ask code-level questions or if you're stuck with a specific error. Read through the [existing questions](https://stackoverflow.com/questions/tagged/docusaurus) tagged with **docusaurus** or [ask your own](https://stackoverflow.com/questions/ask?tags=docusaurus)!

There are many online forums which are a great place for discussion about best practices and application architecture as well as the future of Docusaurus. If you have an answerable code-level question, Stack Overflow is usually a better fit.

- [#docusaurus-2-dev](https://discord.gg/6g6ASPA) for contributing help

- [Reddit's Docusaurus community](https://www.reddit.com/r/docusaurus/)

For new feature requests, you can create a post on our [Canny board](/feedback), which is a handy tool for roadmapping and allows for sorting by upvotes, which gives the core team a better indicator of what features are in high demand, as compared to GitHub issues which are harder to triage. Refrain from making a Pull Request for new features (especially large ones) as someone might already be working on it or will be part of our roadmap. Talk to us first!

For the latest news about Docusaurus, [follow **@docusaurus** on Twitter](https://twitter.com/docusaurus) and the [official Docusaurus blog](/blog) on this website.

StudentFellowsTeamRow,

} from '@site/src/components/TeamProfileCards';

The Docusaurus team works on the core functionality, plugins for the classic theme, as well as the Docusaurus documentation website.

Current members of the Docusaurus team are listed in alphabetical order below.

<ActiveTeamRow />

Docusaurus would never be what it is today without the huge contributions from these folks who have moved on to bigger and greater things.

<HonoraryAlumniTeamRow />

A handful of students have also worked on Docusaurus as part of their school term/internship and the [Major League Hacking Fellowship program](https://fellowship.mlh.io/), contributing amazing features such as plugin options validation, migration tooling, and a Bootstrap theme.

<StudentFellowsTeamRow />

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:

slug: /docusaurus.config.js

`docusaurus.config.js` contains configurations for your site and is placed in the root directory of your site.

- Type: `string`

};

- Type: `string`

};

- Type: `string`

};

- Type: `string`

};

- Type: `Object`

- `label`: the label to use for this locale

- `direction`: `ltr` (default) or `rtl` (for [right-to-left languages](https://developer.mozilla.org/en-US/docs/Glossary/rtl) like Araric, Hebrew, etc.)

- Type: `boolean`

};

- Type: `'ignore' | 'log' | 'warn' | 'error' | 'throw'`

- Type: `'ignore' | 'log' | 'warn' | 'error' | 'throw'`

The behavior of Docusaurus, when it detects any broken markdown link.

By default, it prints a warning, to let you know about your broken markdown link, but you can change this security if needed.

- Type: `'ignore' | 'log' | 'warn' | 'error' | 'throw'`

The behavior of Docusaurus when it detects any [duplicate routes](/guides/creating-pages.md#duplicate-routes).

By default, it displays a warning after you run `yarn start` or `yarn build`.

- Type: `string`

};

- Type: `string`

};

- Type: `string`

};

- Type: `string`

};

- Type: `Object`

};

};

};

};

Docusaurus guards `docusaurus.config.js` from unknown fields. To add a custom field, define it on `customFields`.

Error: The field(s) 'foo', 'bar' are not recognized in docusaurus.config.js

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>`.

};

An array of client modules to load globally on your site:

See also: [`getClientModules()`](lifecycle-apis.md#getclientmodules).

An HTML template written in [Eta's syntax](https://eta.js.org/docs/syntax#syntax-overview) that will be used to render your application. This can be used to set custom attributes on the `body` tags, additional `meta` tags, customize the `viewport`, etc. Please note that Docusaurus will rely on the template to be correctly structured in order to function properly, once you do customize it, you will have to make sure that your template is compliant with the requirements from `upstream`.

An array of CSS sources to load. The values can be either strings or plain objects of attribute-value maps. The `<link>` tags will be inserted in the HTML `<head>`.

- Type: `string`

- Type: `boolean`

We provide official Docusaurus plugins.

These plugins are responsible to load your site's content, and create 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)

These plugins will add a useful behavior to your Docusaurus site.

```bash npm2yarn

npm install --save @docusaurus/plugin-client-redirects

Main usecase: you have `/myDocusaurusPage`, and you want to redirect to this page from `/myDocusaurusPage.html`: