Skip to content

Commit b5a0f8d

Browse files
committed
2 parents 576eb2a + afd16b8 commit b5a0f8d

File tree

4 files changed

+594
-11
lines changed

4 files changed

+594
-11
lines changed

docs/README.md

Lines changed: 23 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,27 +11,46 @@ Content:
1111
5. Getting started: some basic API queries explained.
1212
6. How to guides - for developers who want to use the API
1313

14-
## Install & launch a local documentation server
14+
## Work on the documentation
15+
16+
### Install the documentation tools
1517

1618
Documentation is generated from markdown using `mkdocs` with the `material` theme.
1719

1820
```bash
19-
# install mkdocs and its extensions
21+
# (preferred) Install mkdocs and its extensions
22+
poetry install --with docs
23+
24+
# (old way) install mkdocs and its extensions
2025
pip install mkdocs mkdocs-render-swagger-plugin mkdocs-material mkdocs-macros-plugin
2126
```
2227

2328
💡 Do not mixup _pip_ and _brew_ installation of `mkdocs` (see [troubleshooting](https://jimandreas.github.io/mkdocs-material/troubleshooting/)).
2429

30+
### Launch a local documentation server
31+
2532
```bash
33+
# If mkdocs is installed via poetry (preferred)
34+
# from the root of the cloned repository
35+
cd docs
36+
poetry run mkdocs serve
37+
```
38+
39+
```bash
40+
# If mkdocs is installed globally
2641
# from the root of the cloned repository
2742
cd docs
2843
mkdocs serve
2944
```
3045

3146
Open <http://localhost:8080>
3247

33-
## Access latest published documentation using docker
48+
### Verify the links
3449

3550
```bash
36-
docker run ghcr.io/boavizta/tools-doc:latest
51+
cd docs
52+
# Check the warnings in the output for broken links
53+
poetry run mkdocs build
54+
# Test validity of external links
55+
poetry run poetry run linkcheckMarkdown --recurse --verbose docs
3756
```

docs/docs/Explanations/auto_complete.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ Any calculation using the API is made easier thanks to the **data auto-complete
44

55
the API implements several approaches to complete the missing information:
66

7-
* ```COMPELETE``` : The API infer the value based on the user inputs (e.g. `manufacturer` and `family` for a CPU ```name```).
7+
* ```COMPLETE``` : The API infer the value based on the user inputs (e.g. `manufacturer` and `family` for a CPU ```name```).
88
* ```DEFAULT``` : The API use a default value for those missing attributes (e.g. europe for the default ```usage_location```). The default values can be set in the [configuration file](../config.md).
9-
* ```ARCETYPE``` : The API can use a value taken from an [archetype](archetypes.md).
9+
* ```ARCHETYPE``` : The API can use a value taken from an [archetype](archetypes.md).
1010
* ```CHANGED```: The API can change the value of an attribute to make the computation possible. This happens when you provide a value that is close to the value of an attribute but not exactly the same. For example, if you provide a ```family``` that is not in the database but is close to a family in the database, the API will change the ```family``` to the closest name in the database.
1111

1212
The documentation about how attributes are auto-completed is given on each asset's documentation page.

0 commit comments

Comments
 (0)