docs linkgenerated broken on local

[c0ncentus]

Describe the bug
when npx fliegdoc build and then

on local have link broken

or even worse

To Reproduce
Basic usage, no config

1. whatever project
2. npm i --save fliegdoc && npx fliegdoc build
3. open index.html on doc/
4. See error on links

Expected behavior
userelative instead "/index.html"
and "/lord_ts/index.html".

works on local and on a website router rendering ...

Desktop (please complete the following information):

• OS: Windows 10
• Browser Firefox latest

[pklaschka]

Thanks for creating the issue!

At the moment, the individual views (which could be seen as components for various pieces of the documentation) work without knowing “which file it is in“, so to speak, making handling links a lot easier (not requiring conditional logic). However, this would need to change for relative links to work correctly.

Since there are two “serve” options (one for the built documentation with fliegdoc build -s, and one without building the docs in the file system with fliegdoc serve), I don’t see such support as a high priority for this project (which I want to be focused more on being somewhat minimalistic with a dedicated focus to a limited set of capabilities).

If someone wants to contribute to this feature, I'm happy to discuss (and potentially then accept) contributions if the following requirements are met:

1. the feature is optional (also allowing for absolute links, which can be helpful in some cases), e.g., by providing a ./ as the base URL in the config file
2. no complexity in the template/view files (they should be focused on their structure and not resolving links)
3. URLs remain pretty by default (i.e., not explicitly including index.html).
4. the full (no config needed, out of the box) compatibility with online deployment environments, both with and without trailing slashes, has the highest priority

I will keep this issue open in case anyone wants to take this on, but I don't consider this a priority and will probably not implement it myself.