Getting to the Doom module index is too hard

[pmiddend]

I confirm that...

• I searched the FAQ, issue tracker, discussions board, documentation, and wiki, and found nothing about my issue.

• I read the debugging guide and researched the issue to the best of my ability.

• My issue can be observed on the latest available commit of Doom.

• My issue can be observed on a stable release of Emacs (i.e. doesn't end in .50, .60, or .9*)

Describe your issue

I frequently want to browse the documentation for a specific module. Here are a few issues with this:

1. Say I want the documentation for the "eshell" module. I can duckduckgo "doom emacs eshell" and voila, I get this link which is actually perfect. Okay. Now that I'm already in the docs, I want to go to the overview of other modules. So I click "Back to module index", which links to a 404 page. Other links are broken as well, like the FAQ and even the Help link at the top.
2. Say I don't have Doom emacs yet and want to discover it by going to the Main GitHub page for doomemacs. There, I find a link in the sentence "Doom is comprised of ~150 optional modules, some of which may have additional dependencies. Visit their documentation or run bin/doom doctor to check for any that you may have missed.". However, both of these links are broken.
3. If I open, for example, the FAQ, the document starts with "Our documentation was designed to be read in Doom Emacs (M-x doom/help) or online at https://docs.doomemacs.org/. Avoid reading it elsewhere (like Github) where it will be rendered incorrectly.". When I open my Doom emacs and do M-x doom/help, I indeed get the Doom help page. Clicking the first "Module appendix" link on that page, I get "No match - create this as a new heading?". Clicking the second "Module appendix" link further below, I get an empty emacs/docs/moduels.org buffer.

This is all very frustrating and I think it would be nice to fix all this and make documentation a bit more coherent for newer users.

Steps to reproduce

Described above.

System information

https://pastebin.com/rNMAtKig

[hlissner]

Yes, I'm aware of the state of the documentation and am working on it.