Skip to main content
Version: 2.x

Creating Pages

In this section, we will learn about creating pages in Docusaurus.

The @docusaurus/plugin-content-pages plugin empowers you to create one-off standalone pages like a showcase page, playground page, or support page. You can use React components, or Markdown.


Pages do not have sidebars, only docs do.


Check the Pages Plugin API Reference documentation for an exhaustive list of options.

Add a React page​

React is used as the UI library to create pages. Every page component should export a React component, and you can leverage the expressiveness of React to build rich and interactive content.

Create a file /src/pages/helloReact.js:

import React from 'react';
import Layout from '@theme/Layout';

export default function Hello() {
return (
<Layout title="Hello" description="Hello React Page">
display: 'flex',
justifyContent: 'center',
alignItems: 'center',
height: '50vh',
fontSize: '20px',
Edit <code>pages/helloReact.js</code> and save to reload.

Once you save the file, the development server will automatically reload the changes. Now open http://localhost:3000/helloReact and you will see the new page you just created.

Each page doesn't come with any styling. You will need to import the Layout component from @theme/Layout and wrap your contents within that component if you want the navbar and/or footer to appear.


You can also create TypeScript pages with the .tsx extension (helloReact.tsx).

Add a Markdown page​

Create a file /src/pages/

title: my hello page title
description: my hello page description
hide_table_of_contents: true

# Hello

How are you?

In the same way, a page will be created at http://localhost:3000/helloMarkdown.

Markdown pages are less flexible than React pages because it always uses the theme layout.

Here's an example Markdown page.


You can use the full power of React in Markdown pages too, refer to the MDX documentation.


If you are familiar with other static site generators like Jekyll and Next, this routing approach will feel familiar to you. Any JavaScript file you create under /src/pages/ directory will be automatically converted to a website page, following the /src/pages/ directory hierarchy. For example:

  • /src/pages/index.js β†’ [baseUrl]
  • /src/pages/foo.js β†’ [baseUrl]/foo
  • /src/pages/foo/test.js β†’ [baseUrl]/foo/test
  • /src/pages/foo/index.js β†’ [baseUrl]/foo/

In this component-based development era, it is encouraged to co-locate your styling, markup, and behavior together into components. Each page is a component, and if you need to customize your page design with your own styles, we recommend co-locating your styles with the page component in its own directory. For example, to create a "Support" page, you could do one of the following:

  • Add a /src/pages/support.js file
  • Create a /src/pages/support/ directory and a /src/pages/support/index.js file.

The latter is preferred as it has the benefits of letting you put files related to the page within that directory. For example, a CSS module file (styles.module.css) with styles meant to only be used on the "Support" page.


This is merely a recommended directory structure, and you will still need to manually import the CSS module file within your component module (support/index.js).

By default, any Markdown or JavaScript file starting with _ will be ignored and no routes will be created for that file (see the exclude option).

β”œβ”€β”€ src
β”‚ └── pages
β”‚ β”œβ”€β”€ styles.module.css
β”‚ β”œβ”€β”€ index.js
β”‚ β”œβ”€β”€ _ignored.js
β”‚ β”œβ”€β”€ _ignored-folder
β”‚ β”‚ β”œβ”€β”€ Component1.js
β”‚ β”‚ └── Component2.js
β”‚ └── support
β”‚ β”œβ”€β”€ index.js
β”‚ └── styles.module.css

All JavaScript/TypeScript files within the src/pages/ directory will have corresponding website paths generated for them. If you want to create reusable components into that directory, use the exclude option (by default, files prefixed with _, test files(.test.js), and files in __tests__ directory are not turned into pages).

Duplicate Routes​

You may accidentally create multiple pages that are meant to be accessed on the same route. When this happens, Docusaurus will warn you about duplicate routes when you run yarn start or yarn build, but the site will still be built successfully. The page that was created last will be accessible, but it will override other conflicting pages. To resolve this issue, you should modify or remove any conflicting routes.