-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Move bigbluebutton-docs to the main repository #16113
docs: Move bigbluebutton-docs to the main repository #16113
Conversation
…eta-1 chore: Merge BBB 2.6.0-beta.1 into develop
…-to-be-interrupted fix(ci): Allow builds to be interrupted
chore: Merge BBB 2.6.0-beta.2 into develop
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
(Note to self/Ghazi) We'll likely need to copy over any docs changes from https://github.com/bigbluebutton/bigbluebutton.github.io/commits/master |
SonarCloud Quality Gate failed. 1 Bug No Coverage information |
Just talking with @danimo @schrd @tibroc and others and the consensus is that the work in this PR is a huge leap forward in a desired direction. BIG Thanks to @GhaziTriki @JeanPluzo @lkiesow @danimo and anyone else who has contributed. Merging this will allow others to contribute more easily even while this docs version is being built. |
Background
During BigBlueButton Developer Summit XVI held in Berlin, Germany from Nov 28 to Dec 2nd of year 2022, the community decided to rework the official documentation to make it better.
The initial work has been done in the following repository https://github.com/riadvice/bigbluebutton-docs
Contributors
This work could not be possible without the direct help of (in the contribution order):
What does this PR do?
Move the official documentation with its actual content but reworked structure to the main repository.
Motivation & Context
The current documentation lacks of:
→ The new documentation is now split in 6 main sections.
→ A search engine is now included.
→ Documentation is now part of the main repository. Development and feature documentation should go more in parallel.
→ Each version is now maintained in its own branch.
Tasks
Required for merge
Nice-to-have
To do later