The docs feature provides users with a way to organize Markdown files in a hierarchical format.

Document ID

Every document has a unique id. By default, a document id is the name of the document (without the extension) relative to the root docs directory.
For example, greeting.md id is greeting and guide/hello.md id is guide/hello.
website # Root directory of your site
└── docs
   ├── greeting.md
   └── guide
      └── hello.md
However, the last part of the id can be defined by user in the front matter. For example, if guide/hello.md's content is defined as below, its final id is guide/part1.
---
id: part1
---
Lorem ipsum
If you want more control over the last part of the document URL, it is possible to add a slug (defaults to the id).
---
id: part1
slug: part1.html
---
Lorem ipsum
note
It is possible to use:
  • absolute slugs: slug: /mySlug, slug: /...
  • relative slugs: slug: mySlug, slug: ./../mySlug...

Home page docs

If you want a document to be available at the root, and have a path like https://v2.docusaurus.io/docs/, you can use the slug frontmatter:
---
id: my-home-doc
slug: /
---
Lorem ipsum
To generate a sidebar to your Docusaurus site, you need to define a file that exports a sidebar object and pass that into the @docusaurus/plugin-docs plugin directly or via @docusaurus/preset-classic.
module.exports = {
  // ...
  presets: [
    [
      '@docusaurus/preset-classic',
      {
        docs: {
          // Sidebars filepath relative to the site dir.
          sidebarPath: require.resolve('./sidebars.js'),
        },
        // ...
      },
    ],
  ],
};

Hideable sidebar

Using the enabled themeConfig.hideableSidebar option, you can make the entire sidebar hided, allowing you to better focus your users on the content. This is especially useful when content consumption on medium screens (e.g. on tablets).
module.exports = {
  // ...
  themeConfig: {
    hideableSidebar: true,
    // ...
  },
};
A sidebar object is defined like this:
type Sidebar = {
  [sidebarId: string]:
    | {
        [sidebarCategory: string]: SidebarItem[];
      }
    | SidebarItem[];
};
Below is an example of a sidebar object. The key docs is the id of the sidebar (can be renamed to something else) and Getting Started is a category within the sidebar. greeting and doc1 are both sidebar item.
module.exports = {
  docs: {
    'Getting started': ['greeting'],
    Docusaurus: ['doc1'],
  },
};
Keep in mind that EcmaScript does not guarantee Object.keys({a,b}) === ['a','b'] (yet, this is generally true). If you don't want to rely on iteration order of JavaScript object keys for the category name, the following sidebar object is also equivalent of the above shorthand syntax.
module.exports = {
  docs: [
    {
      type: 'category',
      label: 'Getting Started',
      items: ['greeting'],
    },
    {
      type: 'category',
      label: 'Docusaurus',
      items: ['doc1'],
    },
  ],
};
You can also have multiple sidebars for different Markdown files by adding more top-level keys to the exported object.
Example:
module.exports = {
  firstSidebar: {
    'Category A': ['doc1'],
  },
  secondSidebar: {
    'Category A': ['doc2'],
    'Category B': ['doc3'],
  },
};
As the name implies, SidebarItem is an item defined in a Sidebar. There are a few types we support:

Doc

type SidebarItemDoc =
  | string
  | {
      type: 'doc';
      id: string;
    };
Sidebar item type that links to a doc page. Example:
{
  type: 'doc',
  id: 'doc1', // string - document id
}
Using just the Document ID is perfectly valid as well, the following is equivalent to the above:
'doc1'; // string - document id
Note that using this type will bind the linked doc to current sidebar, this means that if you access doc1 page, the sidebar displayed will be the sidebar this item is on. For below case, doc1 is bounded to firstSidebar.
module.exports = {
  firstSidebar: {
    'Category A': ['doc1'],
  },
  secondSidebar: {
    'Category A': ['doc2'],
    'Category B': ['doc3'],
  },
};
type SidebarItemLink = {
  type: 'link';
  label: string;
  href: string;
};
Sidebar item type that links to a non-document page. Example:
{
  type: 'link',
  label: 'Custom Label', // The label that should be displayed (string).
  href: 'https://example.com' // The target URL (string).
}

Ref

type SidebarItemRef = {
  type: 'ref';
  id: string;
};
Sidebar item type that links to doc without bounding it to the sidebar. Example:
{
  type: 'ref',
  id: 'doc1', // Document id (string).
}

Category

This is used to add hierarchies to the sidebar:
type SidebarItemCategory = {
  type: 'category';
  label: string; // Sidebar label text.
  items: SidebarItem[]; // Array of sidebar items.
  collapsed: boolean; // Set the category to be collapsed or open by default
};
As an example, here's how we created the subcategory for "Docs" under "Guides" in this site:
module.exports = {
  docs: {
    Guides: [
      'creating-pages',
      {
        type: 'category',
        label: 'Docs',
        items: ['markdown-features', 'sidebar', 'versioning'],
      },
    ],
  },
};
Note: it's possible to use the shorthand syntax to create nested categories:
module.exports = {
  docs: {
    Guides: [
      'creating-pages',
      {
        Docs: ['markdown-features', 'sidebar', 'versioning'],
      },
    ],
  },
};

Collapsible categories

For sites with a sizable amount of content, we support the option to expand/collapse a category to toggle the display of its contents. Categories are collapsible by default. If you want them to be always expanded, set themeConfig.sidebarCollapsible to false:
module.exports = {
  // ...
  themeConfig: {
    sidebarCollapsible: false,
    // ...
  },
};

Expanded categories by default

For docs that have collapsible categories, you may want more fine-grain control over certain categories. If you want specific categories to be always expanded, you can set collapsed to false:
module.exports = {
  docs: {
    Guides: [
      'creating-pages',
      {
        type: 'category',
        label: 'Docs',
        collapsed: false,
        items: ['markdown-features', 'sidebar', 'versioning'],
      },
    ],
  },
};

Docs-only mode

If you only want the documentation feature, you can run your Docusaurus 2 site without a landing page and display your documentation page as the index page instead.
To enable docs-only mode, set the docs plugin routeBasePath: '/', and use the frontmatter slug: / on the document that should be the index page (more infos).
caution
You should delete the existing homepage at ./src/pages/index.js, or else there will be two files mapping to the same route!
tip
There's also a "blog-only mode" for those who only want to use the blog feature of Docusaurus 2. You can use the same method detailed above. Follow the setup instructions on Blog-only mode.