mkdocs serve warning

[MaxOstrowski]

INFO    -  Building documentation...
INFO    -  Cleaning site directory
WARNING -  Doc file 'community/DEVELOPMENT.md' contains a link 'tests/test_encoding.py', but the target 'community/tests/test_encoding.py' is not found among documentation files.
INFO    -  Doc file 'community/DEVELOPMENT.md' contains an unrecognized relative link 'tests/example/performance', it was left as is.
INFO    -  Documentation built in 3.37 seconds
INFO    -  [13:57:08] Serving on http://127.0.0.1:8000/systems/constraint_handler/

[VictosVertex]

This happens because currently the file DEVELOPMENT.md from the root directory directly feeds into the mkdocs documentation. That's how our current python template is setup.

The file now contains these links:

• [tests/test_encoding.py](tests/test_encoding.py)
• [tests/example/performance](tests/example/performance)

While this works for editor-rendered markdown, these are links to local directories. Mkdocs however is designed to generate online documentation (even if you can run it on a local server) where these links cannot be resolved, because the code directories are not part of the documentation.

I see several ways to fix this:

1. Not using DEVELOPMENT.md directly in the documentation and keep it as a quick reference for people who do not want to run the full docu
2. Not using local links and instead just name the paths.
3. On documentation generation, hook into the markdown resolution and try to resolve local links to links to the github repository instead. (I have similar hooks in place already for other link resolutions. I would just have to find a way to easily identify local links.)