DOC: Add link to NEPs in top navbar

[melissawm]

From numpy.org it is not obvious how to get to the NEPs page. Unless you know the number of a specific NEP or know the URL, there are no (obvious) links pointing to them. This PR adds a link to the NEPs index from the main User Guide menu.

This may not be the best place to link, better suggestions are welcome.

[charris]

I agree that NEPs need to be more visible, but this still seems a bit hidden. Is there a higher level where they could be linked?

[melissawm]

A few thoughts:

1. We could have a link to the neps from the "Useful links" rubric on https://numpy.org/devdocs/index.html (I'd maybe do this regardless of where the other link lives)
2. I think the NEPs are probably more relevant to developers and to anyone checking the API reference than users, so one idea would be to move it out of the user guide and link it at the bottom of the toc on https://numpy.org/devdocs/reference/index.html and/or https://numpy.org/devdocs/dev/index.html
3. Another thought: Have the "Extras" section of the toc from the user guide be a sidebar element, so that it shows at the bottom of the left sidebar on all sections. One could argue that the glossary, license, release notes and NEPs are relevant enough to be there in all pages.

What do you think?

[melissawm]

For item 3, here's what I mean: https://output.circle-artifacts.com/output/job/1d120789-bcdc-47c0-8670-d819e5a38f02/artifacts/0/doc/build/html/index.html

(for a final version I'll remove it from the main landing page)

[charris]

Is the space between : and // intended? It seems to work, but is somewhat unusual. None of the links work in the circleci generated document, but that is probably unrelated.

[seberg]

That last version looks good to me, I suspect it could be more prominent, but I can't think of a better place. I could see adding them as text on the landing page since we already have links to the old docs, etc. but not sure and no need to do it here.

[rossbar]

How about putting a link to the NEPs in the navigation bar - that is quite prominent and of course visible on every page.

[melissawm]

@rossbar I am ok with that solution as well, but here's how it looks locally:

We would need to either customize the width of the navbar or remove some other item, I'm afraid...

[rossbar]

We would need to either customize the width of the navbar

I'd vote for this - other projects (e.g. scipy, networkx) have both more and longer items in the navbar, and I think we have plenty of room without it looking cluttered! Then again, I don't know exactly what we'd need to do to get the theme configured the way we want...

[melissawm]

Ok - it's easier than I realized! Here's the NEPs link in the top navbar:

https://output.circle-artifacts.com/output/job/1372f4dd-eccd-40d9-9b5f-21311b4aa94b/artifacts/0/doc/build/html/index.html

[Mukulikaa]

Looks good. Thanks, Melissa!