Lifecycle APIs
caution
This section is a work in progress.
Lifecycle APIs are shared by Themes and Plugins.
getPathsToWatch()
Specifies the paths to watch for plugins and themes. The paths are watched by the dev server so that the plugin lifecycles are reloaded when contents in the watched paths change. Note that the plugins and themes modules are initially called with context
and options
from Node, which you may use to find the necessary directory information about the site.
Example:
async loadContent()
Plugins should use this lifecycle to fetch from data sources (filesystem, remote API, headless CMS, etc) or doing some server processing.
For example, this plugin below return a random integer between 1 to 10 as content;
async contentLoaded({content, actions})
Plugins should use the data loaded in loadContent
and construct the pages/routes that consume the loaded data (optional).
async routesLoaded(routes)
Plugins can modify the routes that were generated by all plugins. routesLoaded
is called after contentLoaded
hook.
content
contentLoaded
will be called after loadContent
is done, the return value of loadContent()
will be passed to contentLoaded
as content
.
actions
actions
contain two functions:
addRoute(config: RouteConfig): void
Create a route to add to the website.
createData(name: string, data: any): Promise<string>
A helper function to help you write some data (usually a string or JSON) to disk with in-built caching. It takes a file name relative to to your plugin's directory (name), your data (data), and will return a path to where the data is created.
For example, this plugin below create a /roll
page which display "You won xxxx" to user.
configureWebpack(config, isServer, utils)
Modifies the internal webpack config. If the return value is a JavaScript object, it will be merged into the final config using webpack-merge
. If it is a function, it will be called and receive config
as the first argument and an isServer
flag as the argument argument.
config
configureWebpack
is called with config
generated according to client/server build. You may treat this as the base config to be merged with.
isServer
configureWebpack
will be called both in server build and in client build. The server build receives true
and the client build receives false
as isServer
.
utils
The initial call to configureWebpack
also receives a util object consists of three functions:
getStyleLoaders(isServer: boolean, cssOptions: {[key: string]: any}): Loader[]
getCacheLoader(isServer: boolean, cacheOptions?: {}): Loader | null
getBabelLoader(isServer: boolean, babelOptions?: {}): Loader
You may use them to return your webpack configures conditionally.
For example, this plugin below modify the webpack config to transpile .foo
file.
postBuild(props)
Called when a (production) build finishes.
Example:
extendCli(cli)
Register an extra command to enhance the CLI of docusaurus. cli
is commander object.
Example:
injectHtmlTags()
Inject head and/or body HTML tags to Docusaurus generated HTML.
Example:
getThemePath()
Returns the path to the directory where the theme components can be found. When your users calls swizzle
, getThemePath
is called and its returned path is used to find your theme components.
If you use the folder directory above, your getThemePath
can be:
getClientModules()
Returns an array of paths to the modules that are to be imported in the client bundle. These modules are imported globally before React even renders the initial UI.
As an example, to make your theme load a customCss
object from options
passed in by the user:
Example
Here's a mind model for a presumptuous plugin implementation.