Docusaurus Client API
Docusaurus provides some APIs on the clients that can be helpful to you when building your site.
Components
<Head/>
This reusable React component will manage all of your changes to the document head. It takes plain HTML tags and outputs plain HTML tags and is beginner-friendly. It is a wrapper around React Helmet.
Usage Example:
Nested or latter components will override duplicate usages:
Outputs
<Link/>
This component enables linking to internal pages as well as a powerful performance feature called preloading. Preloading is used to prefetch resources so that the resources are fetched by the time the user navigates with this component. We use an IntersectionObserver
to fetch a low-priority request when the <Link>
is in the viewport and then use an onMouseOver
event to trigger a high-priority request when it is likely that a user will navigate to the requested resource.
The component is a wrapper around react-router’s <NavLink>
component that adds useful enhancements specific to Docusaurus. All props are passed through to react-router’s <NavLink>
component.
to
: string
The target location to navigate to. Example: /docs/introduction
.
activeClassName
: string
The class to give the <Link>
when it is active. The default given class is active
. This will be joined with the className
prop.
<Redirect/>
Rendering a <Redirect>
will navigate to a new location. The new location will override the current location in the history stack, like server-side redirects (HTTP 3xx) do. You can refer to React Router's Redirect documentation for more info on available props.
Example usage:
Hooks
useDocusaurusContext
React hook to access Docusaurus Context. Context contains siteConfig
object from docusaurus.config.js.
Usage example:
useBaseUrl
React hook to automatically prepend baseUrl
to a string automatically. This is particularly useful if you don't want to hardcode your config's baseUrl
. We highly recommend you to use this.
Example usage:
Modules
ExecutionEnvironment
A module which exposes a few boolean variables to check the current rendering environment. Useful if you want to only run certain code on client/server or need to write server-side rendering compatible code.
Field | Description |
---|---|
ExecutionEnvironment.canUseDOM | true if on client, false if SSR. |
ExecutionEnvironment.canUseEventListeners | true if on client and has window.addEventListener . |
ExecutionEnvironment.canUseIntersectionObserver | true if on client and has IntersectionObserver . |
ExecutionEnvironment.canUseViewport | true if on client and has window.screen . |