A user may go to a stellar-core page with the url https://www.stellar.org/developers/stellar-core/learn/admin.html. Out of curiosity, the user deletes the learn/admin.html and gets to https://www.stellar.org/developers/stellar-core/. However, that root stellar-core page looks like this:

Why?
This happens because all pages on the developer site is supposed to be under one of the four categories: Learn, Reference, Tools, and Beyond Code. It was decided a while back that some files did not need to be put on the developers site and thus were not categorized (not in a folder with the above name).
There are two solutions
Option 1: Exclude non-categorized files in build process
In the gulp process, instead of symlinking to the project docs page, we can symlink to these specific four folders.
Option 2: Include these files by categorizing them
This would involve moving the files from the docs folder root to their specific folders.
A user may go to a stellar-core page with the url
https://www.stellar.org/developers/stellar-core/learn/admin.html. Out of curiosity, the user deletes thelearn/admin.htmland gets tohttps://www.stellar.org/developers/stellar-core/. However, that root stellar-core page looks like this:Why?
This happens because all pages on the developer site is supposed to be under one of the four categories:
Learn,Reference,Tools, andBeyond Code. It was decided a while back that some files did not need to be put on the developers site and thus were not categorized (not in a folder with the above name).There are two solutions
Option 1: Exclude non-categorized files in build process
In the gulp process, instead of symlinking to the project docs page, we can symlink to these specific four folders.
Option 2: Include these files by categorizing them
This would involve moving the files from the
docsfolder root to their specific folders.