Doc site repository structure
This page describes the function of each file in your new doc site, based on this repository.
1 directory, 5 files
Contains all the GitHub actions for the repository.
Action that builds the docs as they would be built in production, to check for any build errors.
Action that ensures that all Markdown files have file names which are only lower case letters, digits, dashes, or underscores.
Action that runs
npm run lint from
It includes spell checking, TypeScript linting, and CSS styling.
Action that builds and deploys the docs to GitHub Pages when any commit is made to the
Action that checks all recent commits made to
main branch and automatically cuts a release in line
with semantic versioning.
This action reads the configuration in
.releaserc.js in the root directory of this repository.
Contains all the Markdown and related files for the blog functionality of Docusaurus.
Contains all the Markdown and related files for the docs functionality of Docusaurus.
Contains all the JSX and CSS files for the pages functionality of Docusaurus.
│ └── HomepageFeatures
│ ├── index.tsx
│ └── styles.module.css
│ └── custom.css
5 directories, 6 files
Contains JSX components for React.js which should live separately from the
JSX components are broken up here with
.tsx extensions and accompanying scoped
You can then import these components into files in the
Contains any non-scoped CSS files.
We recommend leaving the default
custom.css file by itself in this folder and not add any other files.
custom.css is the global styles file
that applies to the entire doc site.
Pages are one-off standalone pages that don't have sidebars by default.
You can still add a Markdown page to
this folder, and it will be rendered with the file name as the path.
Routing is file-based for any
Contains assets that can be directly copied on build output. Usually images, stylesheets, favicons, fonts, etc.
See how to reference your static asset.
2 directories, 7 files
A spell checker configuration file used in linting to check for misspelling in all files.
Includes basic configuration with
ignorePaths for paths/files which should not be checked.
You can add additional dictionaries, either default supported or additional files, such as the
project-words.txt file included in this repository.
EditorConfig is supported by most IDEs and text editors to provide consistent coding styles for projects using a configuration specification.
.eslintignore file contains a list of directories for ESLint to ignore when linting.
Configuration for ESLint and accompanying plugins used by it to parse and lint the code.
A file containing files and folders for Git to ignore when adding or committing.
Contains the Node.js version to use for this project. It requires installing nvm.
We recommend using Prettier to format all files.
Anything not covered in
.editorconfig is overridden or specified in this Prettier configuration file.
npm run format runs Prettier to format and save those changes.
semantic-release is used to easily keep
track of version changes to documentation.
On push to the
main branch, the
release GitHub action takes all necessary commits based on their
type and increments the version according to semver conventions.
However, this is not strictly necessary, and you can remove this along with its accompanying action.
StyleLint is used to lint CSS files. This file ignores directories which do not need to be linted.
StyleLint configuration for linting.
Semantic Release automatically updates the CHANGELOG file with release history and commits appended to each release. You shouldn't modify this manually.
This repository by default has the plugin
docusaurus-plugin-openapi-docs installed to demonstrate
how to integrate OpenAPI documentation directly into Docusaurus.
api.mustache file contains the API template for the plugin when generating the Markdown files.
The Babel configuration used by Docusaurus. You shouldn't modify this.
Contains all major Docusaurus configuration which is necessary to configure its behavior.
Used by npm when
npm install is used to lock versions and reduce differences between development
environments if this isn't committed to the repository.
It should not be necessary to edit this file.
Used by npm and contains configuration scripts, dependencies, development dependencies, and other related dependency configurations.
Used by CSpell in the
.cspell.json configuration file with additional project words that should
not be flagged as misspelling when linting.
.js file used by Docusaurus to provide sidebar configuration.
This project uses Typescript for React.
tsconfig.json contains Typescript compiler options but isn't used in compilation of the
project and is only for editor experience.