You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Roman Donchenko 4c32be5c9b
Fix the documentation build (#5704)
In #5678, I thought that the extra README that eventually ended up in
`cvat-sdk/docs/README.md` was unused, which turned out to be not quite
true. One section from it _was_ used to generate the online API index
page. Since I removed the file, the online docs now fail to build.

Rather than restore the entire README, restore just that one section as
a standalone file. This achieves the same result as before, but with
simpler code.
3 years ago
..
assets Fixed Intel license headers (#119) 4 years ago
content/en Fix typos/misspellings in the documentation (#5687) 3 years ago
i18n Added user_registered signal (#5007) 3 years ago
layouts Added user_registered signal (#5007) 3 years ago
static/favicons Website with documentation (#3039) 5 years ago
templates/en/docs/api_sdk/sdk/reference/apis Extend SDK layer 1 docs (#5011) 3 years ago
themes Update website (#3293) 5 years ago
README.md Improved documentation versioning (#3569) 5 years ago
build_docs.py Add SDK docs (#4928) 3 years ago
config.toml Added user_registered signal (#5007) 3 years ago
package-lock.json Bump nanoid from 3.1.28 to 3.3.1 in /site (#4390) 4 years ago
package.json Remove Intel related information (e.g., links on Intel resources) (#15) 4 years ago
process_sdk_docs.py Fix the documentation build (#5704) 3 years ago
requirements.txt Extend SDK layer 1 docs (#5011) 3 years ago

README.md

Basic manual for website editing

Edit or add documentation pages

To edit and/or add documentation, you need to have a GitHub account. To change documentation files or add a documentation page, simply click Edit this page on the page you would like to edit. If you need to add a child page, click Create child page.

If you need to edit the text that has the markup markdown, click on the Fork this repository button.

Read how to edit files for github (GitHub docs).

Please note that files have a markup for correct display on the site: the title, the title of the link, the weight (affects the order of files display on the sidebar) and description (optional):

---
title: "Title"
linkTitle: "Link Title"
weight: 1
description: >
    Description
---

Start site localy

To start the site locally, you need arecent extended version hugo (recommend version 0.75.0 or later). Open the most recent release and scroll down until you find a list ofExtendedversions. Read more

Add a path to "hugo" in the "Path" environment variable.

Clone a repository branch containing the site. For example, using a git command:

git clone --branch <branchname> <remote-repo-url>

If you want to build and/or serve your sitelocally, you also need to get local copies of the themes own submodules:

git submodule update --init --recursive

To build and preview your site locally, use:

cd <your local directory>/cvat/site/
hugo server

By default, your site will be available athttp://localhost:1313/docs/.

Instead of a "hugo server" command, you can use the "hugo" command that generates the site into a "public" folder.

To build or update your sites CSS resources you will need PostCSS to create final assets. To install it you must have a recent version of NodeJS installed on your machine, so you can use npm, the Node package manager. By default npm installs tools under the directory where you run npm install:

cd <your local directory>/cvat/site/
npm ci

Then you can build a website in the "public" folder:

hugo

Read more

Update the submodule of the docsy theme

To update the submodule of the docsy theme you need to have a repository clone. While in the repository folder, use the git command:

git submodule update --remote

Add and then commit the change to project:

git add themes/
git commit -m "Updating theme submodule"

Push the commit to project repo. For example, run:

git push