Static Assets
Every website needs assets: images, stylesheets, favicons etc. In such cases, you can create a directory named static
at the root of your project.
Every file you put into that directory will be copied into the root of the generated build
folder with the directory hierarchy preserved. E.g. if you add a file named sun.jpg
to the static folder, it will be copied to build/sun.jpg
.
This means that:
- for site
baseUrl: '/'
, the image/static/img/docusaurus.png
will be served at/img/docusaurus.png
. - for site
baseUrl: '/subpath/'
, the image/static/img/docusaurus.png
will be served at/subpath/img/docusaurus.png
.
#
Referencing your static assetYou can reference assets from the static
folder in your code using absolute paths, but this is not ideal because changing the site baseUrl
will break those links.
You can import
/ require()
the static asset (recommended), or use the useBaseUrl
utility function: both prepend the baseUrl
to paths for you.
#
JSX exampleYou can also import SVG files: they will be transformed into React components.
#
Markdown exampleMarkdown links and images referencing assets of the static folder will be converted to require("@site/static/assetName.png")"
, and the site baseUrl will be automatically prepended for you.
Thanks to MDX, you can also use useBaseUrl
utility function in Markdown files! You'd have to use html tags like <img>
instead of the Markdown image syntax though. The syntax is exactly the same as in JSX.
#
CaveatsKeep in mind that:
- By default, none of the files in
static
folder will be post-processed, hashed or minified. - Missing files referenced via hardcoded absolute paths will not be detected at compilation time, and will result in a 404 error.
- By default, GitHub Pages runs published files through Jekyll. Since Jekyll will discard any files that begin with
_
, it is recommended that you disable Jekyll by adding an empty file named.nojekyll
file to yourstatic
directory if you are using GitHub pages for hosting.