Plugins are the building blocks of features in a Docusaurus 2 site. Each plugin handles its own individual feature. Plugins may work and be distributed as part of bundle via presets.
A plugin is usually a npm package, so you install them like other npm packages using npm.
Then you add it in your site's
Docusaurus can also load plugins from your local directory, you can do something like the following:
For the most basic usage of plugins, you can provide just the plugin name or the absolute path to the plugin.
However, plugins can have options specified by wrapping the name and an options object in an array inside your config. This style is usually called
It is possible to use multiple times the same plugin, on the same Docusaurus website.
In this case, it is required to assign a unique id to each plugin instance.
By default, the plugin id is
Docusaurus' implementation of the plugins system provides us with a convenient way to hook into the website's lifecycle to modify what goes on during development/build, which involves (but not limited to) extending the webpack config, modifying the data being loaded and creating new components to be used in a page.
A plugin is a module which exports a function that takes two parameters and returns an object when executed.
The exported modules for plugins are called with two parameters:
For example if you have a reference to a local folder such as this in your
Then in the folder
my-plugin you can create an index.js such as this
my-plugin folder could also be a fully fledged package with it's own package.json and a
src/index.js file for example
context is plugin-agnostic and the same object will be passed into all plugins used for a Docusaurus website. The
context object contains the following fields:
options are the second optional parameter when the plugins are used.
options are plugin-specific and are specified by users when they use them in
docusaurus.config.js. Alternatively, if preset contains the plugin, the preset will then be in charge of passing the correct options into the plugin. It is up to individual plugin to define what options it takes.
The returned object value should implement the lifecycle APIs.