|
1 |
| -chargebyte GmbH Product Documentation |
2 |
| -============================= |
| 1 | +Charge SOM Product Documentation |
| 2 | +================================ |
3 | 3 |
|
4 |
| -Welcome to the documentation for products of chargebyte GmbH. |
| 4 | +This is the product documentation project for the Charge SOM, a product of chargebyte GmbH. |
| 5 | +This documentation is intended for users, developers, and administrators of the Charge SOM. |
| 6 | +This documentation is hosted on Read the Docs and can be accessed at |
| 7 | +https://chargebyte-docs.readthedocs.io/en/latest/. |
5 | 8 |
|
6 |
| -This documentation contains all necessary information and guides for the use and understanding of our products. |
7 | 9 |
|
8 | 10 | Contents:
|
9 | 11 | ---------
|
10 | 12 |
|
11 |
| -- Product specifc User Guides and Manuals (In Progress) |
12 |
| -- Developer Documentation (In Progress) |
13 |
| -- FAQs and Troubleshooting (In Progress) |
| 13 | +- Charge SOM User Guide |
| 14 | + |
| 15 | +Repo initialization: |
| 16 | +------------------- |
| 17 | +This repository is using git submodules to share documents between the user guides. |
| 18 | +After cloning of the project please execute the following command: |
| 19 | + |
| 20 | +git submodule update --init --force --remote |
| 21 | + |
| 22 | + |
| 23 | +Building the documentation locally: |
| 24 | +----------------------------------- |
| 25 | + |
| 26 | +To build the documentation locally, you need to have Python and pip installed on your system. |
| 27 | +You can install the required dependencies by running the following command: |
| 28 | + |
| 29 | +pip install -r requirements.txt |
| 30 | + |
| 31 | +After installing the dependencies, you can build the documentation by running the following command: |
| 32 | + |
| 33 | +sphinx-build -a docs/source {output_directory} |
| 34 | + |
| 35 | +The output directory is the directory where the generated HTML files will be stored. |
| 36 | + |
| 37 | + |
| 38 | +Contributing: |
| 39 | +------------- |
| 40 | + |
| 41 | +If you would like to contribute to the documentation, please fork the repository and create a pull |
| 42 | +request with your changes. Please make sure to follow the guidelines for contributing to the |
| 43 | +documentation: |
| 44 | + |
| 45 | +- The branch name for the pull request should be `everest/csom_{your_branch_name}`. |
| 46 | +- Maximum line length should be 120 characters (Preferably 100 characters). |
| 47 | +- Images should be stored in the `docs/source/_static/images` directory |
| 48 | +- CSS files should be stored in the `docs/source/_static/css` directory |
| 49 | +- Source and config files should be stored in the `docs/source/_static/files` directory |
| 50 | +- A documentation file should be written in reStructuredText format |
| 51 | +- A documentation file should start with referenceable label of the file name (e.g. ".. _hardware.rst:") |
| 52 | +- Sections and chapters should be separated by one blank line after the title and two blank lines before the title |
| 53 | +- Sections with a chapter title before, need to have only one blank line before the title |
| 54 | +- First letters of section and chapter titles should be capitalized (e.g. "Charge SOM User Guide") |
| 55 | + |
| 56 | + |
| 57 | +License: |
| 58 | +-------- |
| 59 | + |
| 60 | +See the LICENSE file for license rights and limitations (Apache 2.0). |
| 61 | + |
14 | 62 |
|
15 | 63 | Contact:
|
16 | 64 | --------
|
17 | 65 |
|
18 | 66 | If you have any questions or inquiries, please contact our support team at https://chargebyte.com/support.
|
19 | 67 |
|
20 | 68 | Thank you for using products from chargebyte GmbH!
|
21 |
| - |
|
0 commit comments