InvenTree/docs
2024-07-30 20:31:16 +10:00
..
_includes [WIP] docker / Caddy (#6551) 2024-02-28 01:06:19 +11:00
ci Add mermaid to docs (#5405) 2024-02-05 21:40:38 +11:00
docs Add how to install custom packages to the docker image section (#7752) 2024-07-30 20:31:16 +10:00
__init__.py Fixes for docs building (#4659) 2023-04-22 23:35:25 +10:00
.gitignore Docs code links (#7342) 2024-05-26 22:09:08 +10:00
extract_schema.py Some small style fixes (#6916) 2024-04-03 19:26:03 +11:00
LICENSE Documentation integration (#4653) 2023-04-22 22:40:29 +10:00
main.py Add detection of curroent commit / branch (#7745) 2024-07-30 12:28:36 +10:00
mkdocs.yml Migrate Icons to Tabler icons and integrate into PUI (#7684) 2024-07-24 12:36:02 +10:00
mlc_config.json Document security measures (#6812) 2024-03-25 09:12:49 +11:00
README.md Improve reproduciblity of image (#7120) 2024-04-29 11:04:45 +10:00
requirements.in Report printing refactor (#7074) 2024-05-22 10:17:01 +10:00
requirements.txt Bump development deps (#7606) 2024-07-18 09:53:17 +10:00

InvenTree Documentation

Documentation Status

This repository hosts the official documentation for InvenTree, an open source inventory management system.

To serve this documentation locally (e.g. for development), you will need to have Python 3 installed on your system.

Setup

Run the following commands from the top-level project directory:

$ git clone https://github.com/inventree/inventree
$ pip install --require-hashes -r docs/requirements.txt

Serve Locally

To serve the pages locally, run the following command (from the top-level project directory):

$ mkdocs serve -f docs/mkdocs.yml -a localhost:8080

Edit Documentation Files

Once the server is running, it will monitor the documentation files for any changes, and update the served pages.

Admonitions

"Admonition" blocks can be added as follow:

!!! info "This is the admonition block title"
    This is the admonition block content

Refer to the reference documentation to customize the admonition block to the use-case (eg. warning, missing, info, etc.).

Links to internal documentation pages must use relative pathing, otherwise the link will be broken by the readthedocs URL formatting.

Also, linking to an internal page must use the .md suffix!

For example, to link to the page /part/views from /stock/stocktake, the link must be formed as follows:

Click [here](../part/views.md)

Formatting the link as follows:

Click [here](/part/views)

will result in a broken link.

Images

Images are served from the ./docs/assets/images folder and can be added as follow:

{% with id="image_id", url="folder/image_name.png", description="Text shown if image is not loaded properly" %}
{% include 'img.html' %}
{% endwith %}

Replace:

  • image_id with a short unique identifier for the image (most commonly, image_id is same as image_name)
  • folder with the folder in docs/assets/images in which the image is stored
  • image_name with the name of the image
  • .png with the image extension (PNG or JPEG are preferred formats)

Global variables

Refer to the reference documentation to find out how to add global variables to the documentation site.

Global variables should be added in the # Global Variables section of the mkdocs.yml configuration file.

Credits

This documentation makes use of the mkdocs-material template