bigbluebutton-Github/docs
2023-03-20 17:16:32 -04:00
..
docs docs: marking 2.6.0 as stable (#17115) 2023-03-20 17:16:32 -04:00
src docs: marking 2.6.0 as stable (#17115) 2023-03-20 17:16:32 -04:00
static Move greenlight v3 docs to this repo 2023-03-06 23:30:40 +01:00
.gitignore Versioning configuration and improvents in the build script 2023-02-09 10:53:47 +01:00
babel.config.js Move bigbluebutton-docs to the main repository. 2022-12-10 21:21:56 +01:00
build.sh docs: enable building of 2.5 docs 2023-03-16 15:18:27 -04:00
docusaurus.config.js docs: enable building of 2.5 docs 2023-03-16 15:18:27 -04:00
package-lock.json Fix broken links in the new docs. 2023-01-12 21:46:29 +01:00
package.json Fix broken links in the new docs. 2023-01-12 21:46:29 +01:00
README.md docs: sync 2.6 customize docs 2023-03-16 09:36:25 -04:00
sidebars.js Move greenlight v3 docs to this repo 2023-03-06 23:30:40 +01:00
tsconfig.json Move bigbluebutton-docs to the main repository. 2022-12-10 21:21:56 +01:00
yarn.lock Fix broken links in the new docs. 2023-01-12 21:46:29 +01:00

BigBlueButton Docs

These docs are automatically built using Docusaurus 2 and GitHub Actions (see deploy-docs.yml).

Local Development

To test build the docs locally you can either use yarn or npm.

$ yarn install  # install docusaurus and dependencies
$ yarn start  # start local dev server

The last command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

There is also a script build.sh that goes through all branches of the repository and adds all release branches that have a docusaurus.config.js-file as versions to the docs. Note that you can not have uncommited local changes before you run /build.sh, otherwise git will refuse to change branches. This step is optional and if you don't run it, docusaurus will only build the currently checkout out version which is recommended for local development (building all the versions locally can lead to problems with the live updates when using yarn start).

Build

If you only want to build the docs you can run:

$ yarn clear # ensure cached content is not interfering with your changes
$ yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.