bigbluebutton-Github/docs
2023-03-10 19:06:02 -05:00
..
docs Update docs/docs/greenlight/v3/customize.md 2023-03-10 19:06:02 -05:00
src Move greenlight v3 docs to this repo 2023-03-06 23:30:40 +01: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 Only build specified versions 2023-03-08 21:10:57 +01:00
docusaurus.config.js Merge pull request #16934 from tibroc/docs-remove-edit-#16863 2023-03-07 09:11:57 -05: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 Update readme 2023-02-09 11:41:39 +01: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
$ ./build.sh  # add all versions to build
$ yarn start  # start local dev server

The script build.sh 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.

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.

Build

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

$ yarn build

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