Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete /hub page #560

Closed
wants to merge 2 commits into from
Closed

Delete /hub page #560

wants to merge 2 commits into from

Conversation

palewire
Copy link
Collaborator

@palewire palewire commented Dec 27, 2021

In the same spirit as #559, I'm putting forward the challenge: Can we live without this page? It's largely redundant of this documentation site. Can we lose it?

@choldgraf
Copy link
Collaborator

I'm on the fence about this one - I think there's value in having a simple landing page for the major sub-projects that can point people in the right direction. I imagine something like http://bokeh.org/ where there's just a splash page, high level use-case information, and pointers to next steps.

https://jupyterhub.readthedocs.io/en/stable/ does have that information, but also a lot of other information, and it's laid out more like a traditional verbose documentation page rather than having lots of UI elements that make it easy to parse.

So I guess what I'm thinking is that:

  • I agree that it's better for us to point to a jupyterhub docs site for this information, rather than putting the copy on jupyter.org
  • but, I don't know of a jupyterhub docs page that has the right high-level information / splash page right now :-/

Sooo...hmmm, thinking out loud a bit: maybe the right path forward is to think about what the end-goal should be, and then take baby steps towards that. I think the goal is to have something like a projects/ page with pointers to other project-specific places, so removing hub/ would be a step in that direction 🤔

@krassowski
Copy link
Member

I outlined my general feeling about this in #529 (comment), but in case if this change was to go forward let me focus on technical aspect here:

The search results for "JupyterHub" in Google include /hub at the first position, so we probably should keep the /hub permalink working and redirect to the new target page (currently proposed to be JupyterHub documentation). This can be achieved by adding a small template as in: https://stackoverflow.com/questions/39657226/jekyll-redirect-link and redirect field.

@choldgraf
Copy link
Collaborator

I added some thoughts over in #529 since that's the more generic topic to discuss.

@palewire
Copy link
Collaborator Author

palewire commented Jan 3, 2022

Following discussion here and in #529, I am withdrawing this proposal.

@palewire palewire closed this Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants