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 0ab445b7a8
Replace unintended Cyrillic C letters with Latin C (#5334)
The only change in production code is the one in `shortcuts-reducer.ts`.
It makes no functional difference, however, because the shortcut in
question is not handled by the regular shortcut mechanism; the control
key is handled separately in `interactionHandler.ts`, while the string
"ctrl" in `shortcuts-reducer.ts` is only used for display purposes.

Fix ESLint errors in altered files, as well.

<!-- Raised an issue to propose your change
(https://github.com/cvat-ai/cvat/issues).
It helps to avoid duplication of efforts from multiple independent
contributors.
Discuss your ideas with maintainers to be sure that changes will be
approved and merged.
Read the
[CONTRIBUTION](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md)
guide. -->

<!-- Provide a general summary of your changes in the Title above -->

### Motivation and context
<!-- Why is this change required? What problem does it solve? If it
fixes an open
issue, please link to the issue here. Describe your changes in detail,
add
screenshots. -->
These Cyrillic Cs interfere with searching and can cause confusion.

### How has this been tested?
<!-- Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc. -->
I'm relying on GitHub Actions.

### Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply.
If an item isn't applicable by a reason then ~~explicitly
strikethrough~~ the whole
line. If you don't do that github will show an incorrect process for the
pull request.
If you're unsure about any of these, don't hesitate to ask. We're here
to help! -->
- [x] I submit my changes into the `develop` branch
- ~~[ ] I have added a description of my changes into
[CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md)
file~~
- ~~[ ] I have updated the [documentation](
https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation)
accordingly~~
- ~~[ ] I have added tests to cover my changes~~
- ~~[ ] I have linked related issues ([read github docs](

https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~
- ~~[ ] I have increased versions of npm packages if it is necessary
([cvat-canvas](https://github.com/cvat-ai/cvat/tree/develop/cvat-canvas#versioning),

[cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning),
[cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning)
and
[cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning))~~

### License

- [x] I submit _my code changes_ under the same [MIT License](
https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the
project.
  Feel free to contact the maintainers if that's a concern.
3 years ago
..
assets Fixed Intel license headers (#119) 4 years ago
content/en Replace unintended Cyrillic C letters with Latin C (#5334) 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 Extend SDK layer 1 docs (#5011) 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