fixing broken links

[choldgraf]

This fixes some broken links that we were manually hardcoding to specific headers on the reference page. Instead we are now programmatically adding Sphinx labels to each section of that page so that we can reference them in a URL-agnostic way.

The new Sphinx labels have the structure:

schema:<object>

For example,

schema:scheduling.podPriority

So you can refer to them directly like Here is my sentence and now I :ref:`refer to pod priority in rST <schema:scheduling.podPriority>` .

closes #1717

[consideRatio]

Wieee and it works :D Thank you @choldgraf !!! 🎉 ❤️ 🌻

[choldgraf]

oh btw - I also ran make linkcheck on the docs and only found one other broken link, so I think that we should be OK now?

[consideRatio]

checking consistency... /home/travis/build/jupyterhub/zero-to-jupyterhub-k8s/doc/source/reference.md: WARNING: document isn't included in any toctree
done
preparing documents... done
writing output... [100%] setup-jupyterhub/turn-off                              
/home/travis/build/jupyterhub/zero-to-jupyterhub-k8s/doc/source/reference.md:1: WARNING: Pygments lexer name 'eval_rst' is not known
/home/travis/build/jupyterhub/zero-to-jupyterhub-k8s/doc/source/reference.md:16: WARNING: Pygments lexer name 'eval_rst' is not known

Ah well... these are open issues still :§ A lot of trouble coming from the generated section :<

[choldgraf]

I think we should be able to remove reference.md, no? It seems like it's just a static version of the programmatically-created one that lives at reference/reference.md, no?

That'd also remove the eval_rst errors, which are carryovers from when we used recommonmark

[consideRatio]

Oh! I didn't realize it's that file: #1822

Yeah, I can go ahead and remove it. I'm feeling a bit vane and will do it by committing in another name to not be associated with that amount of line deletions introduced by mistake :p

[choldgraf]

lol :-)

[consideRatio]

Yepp haha i lolled too realizing this ;D