Only 1 link in sidebar navigation on how-to/index.html

[ThomasFreedman]

The sidebar on this page is almost worthless without the links. For example, the Websites on IPFS heading should be a link to websites-on-ipfs/single-page-website/index.html or a new websites-on-ipfs/index.html that covers all items related to hosting websites already in the docs.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additiona round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.tech if you just need general support.

[ThomasFreedman]

I discovered the issue is related to the web server's doc root. The links in the website should all be relative, so it shouldn't matter if the base of the ipfs documentation tree is located in the doc root or a sub folder of the doc root, but it does matter.

There is something in the left side navigation in the "how-to" folder (Guides) that isn't relative but rather is expected to be in the web servers doc root folder. When the ipfs documentation tree is moved to a subfolder (not in server's doc root), only the first link of left side panel on the "guides" (how-to folder) page fails to function like it does in the doc root of the web server.

[ThomasFreedman]

I discovered the issue is related to the web server's doc root. The links in the website should all be relative, so it shouldn't matter if the base of the ipfs documentation tree is located in the doc root or a sub folder of the doc root, but it does matter.

There is something in the left side navigation in the "how-to" folder (Guides) that isn't relative but rather is expected to be in the web servers doc root folder. When the ipfs documentation tree is moved to a subfolder (not in server's doc root), only the first link of left side panel on the "guides" (how-to folder) page fails to function like it does in the doc root of the web server.