How to use the Projects Plugin - help!

[stevejr]

Hi,

We currently use mkdocs-material for a single set of product documentation and deploy using the standard mkdocs gh-deploy --force command. Our current repository layout has the mkdocs.yml at the root and then a docs folder that contains all of our documentation.

We would now like to have multiple product documentation under the one site with each being served at a specific path i.e. https://my.domain.com/product_a, https://my.domain.com/product_b etc and believe we can do this with the Projects plugin but I am struggling a little to get it working.

My repository has now been amended so that we have the following:

.
├── mkdocs
│   ├── Dockerfile
│   ├── Dockerfile.staging
│   └── requirements.txt
├── mkdocs.yml
├── projects
│   ├── __init__.py
│   └── product_a
│       ├── custom_theme
│       │   ├── img
│       │   │   └── favicon.ico
│       │   └── main.html
│       ├── docs
│       │   ├── admin
│       │   │   └── index.md
....

We create a docker image so we can test the documentation locally. We use a Python 3 base image, pip install mkdocs-material-insiders and then copy in the mkdocs.yml and projects folder. We run the docker image with the command docker run -it --rm docs - the Dockerfile has the command CMD ["serve", "-f", "mkdocs.yml", "--dev-addr=0.0.0.0:8000"] however I am seeing some errors and want to check if this is the correct way to run mkdocs, for example it is looking for a docs folder at the root.

Is the above possible?

[stevejr]

So, I created a docs folder in the root and that error is gone but a new one now occurs:

INFO    -  Building documentation...
ERROR   -  [project://.product_a] Config value 'theme': The path set in custom_dir ('projects/product_a/custom_theme') does not exist.

The path does exist so am struggling as to why I am seeing the error.

Note - when I run the project i.e cd projects/product_a && mkdocs serve -f mkdocs.yml it works fine.