-
Clone the repository
-
The documentation is written using a tool called
docsify
. To installdocsify
, run the following command:npm install -g docsify-cli
-
To run the documentation locally, run the following command:
docsify serve docs
-
Open a browser and navigate to
http://localhost:3000
- Navigate to the
docs
directory - Update the content in the markdown files in the
docs/<subteam>
directory to the respective markdown files in the repository - Update the
_sidebar.md
file with the new content - Commit the changes and push to the repository
- The documentation will be updated automatically
- Navigate to the respective directory where the documentation would be accessed on the website within the
docs
directory - Create a blank markdown file with a placeholder comment at the top of the file ex.
<---Placeholder--->
- In
docs/_sidebar.md
, add a new entry for the documentation with the path to the new markdown file - In
docsify-plugin-test.js
, add a new entry for the documentation in thefilesMap
object with the path to the new markdown file and the URL to the raw markdown file in the repository. Ensure the path follows the format#/subteam/filename
- Commit the changes and push to the repository
docs/cv/onboarding.md
:
1. <---Placeholder--->
2. > Repository: [CV-Onboarding](https://github.com/umigv/CV-Onboarding)
3. ---
docs/_sidebar.md
:
...
- Computer Vision
...
- [Onboarding](cv/onboarding.md)
...
docsify-plugin-test.js
:
const filesMap = {
...
"#/cv/onboarding": "https://raw.githubusercontent.com/umigv/CV-Onboarding/main/README.md",
...
}
- Using direct links to the documentation site for paths that fetch content from other repositories will not work. The content will not be displayed. To access the content, navigate to the respective directory in the sidebar. Finding a solution to this issue.
- External links in the documentation will not work unless the link is to another URL (ex. having a link to another MD file in the external repo). Finding a solution to this issue.