Skip to main content
Version: current

Makersaurus Config

You need a makersaurus.config.js file in the project root to successfully generate a site. Most properties have docusaurus.config.js equivalents and are just copied over - you can refer to the Docusaurus configuration docs for great documentation about exactly what these fields do. Fields specific to Makersaurus are more extensively documented below.

Schema

makersaurus.config.js should export an object with the following properties:

PropertyTypeRequiredReference
baseUrlstringDocusaurus docs
dependenciesobjectRead below
deploymentBranchstringDocusaurus docs
blogobjectBlog docs
disableVersioningbooleanVersioning docs
feedbackAssigneestringFeatures guide
feedbackLabelsarrayFeatures guide
includeCurrentVersionsbooleanVersioning docs
lastVersionstringVersioning docs
markdownobjectDocusaurus docs
oldVersionsHrefstringFeatures guide
projectNamestring*Docusaurus docs
redocusaurusobjectFeatures guide
searchFilterstringFeatures guide
taglinestring*Docusaurus docs
titlestring*Docusaurus docs
themesobjectDocusaurus docs
versionCustomFieldstringFeatures guide
urlstringDocusaurus docs
versionsobjectVersioning docs

Dependencies config

The dependencies object allows you to specify npm packages that you want to use in your docs. For example, to render videos in documentation using react-player, you can add that package to the dependencies object like so:

dependencies: {
"react-player": "^2.11.0"
},

The format is the exact same as in package.json. You can add as many dependencies as you want, though just like any other project remember that installing too many dependencies leads to poor performance.


Feedback