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

[DOCUMENTATION] Add back link to project home page from built docs #458

Open
nigelmegitt opened this issue Jul 13, 2017 · 7 comments
Open

Comments

@nigelmegitt
Copy link
Collaborator

When you traverse from the project home page to the the documentation there are no links back. Add one, preferably in the blue panel in the top left.

@nigelmegitt
Copy link
Collaborator Author

Notes:

the home page looks URL is:

http://ebu.github.io/ebu-tt-live-toolkit/

the built documentation ends up at:

http://ebu.github.io/ebu-tt-live-toolkit/html/index.html

So the back link is effectively ../.. or ../index.html though that backwards links always seem "dodgy" somehow, and I'm not sure how standard they are. It seems like bad practice to use them if avoidable.

@nigelmegitt
Copy link
Collaborator Author

It seems like the most likely way to be able to achieve this is to subclass the template as documented for Sphinx, but my initial attempts resulted in nothing happening, so nothing to commit after looking at this in various different ways for an hour or so. Probably won't come back to this for a while now, if anyone else wants to take a go.

@spoeschel
Copy link
Collaborator

It seems that links to any files in an ancestor folder are not possible. I tried myself (without success) and also found sphinx-doc/sphinx#701.

@nigelmegitt
Copy link
Collaborator Author

Grr that's frustrating @spoeschel ! Thanks for looking.

@spoeschel
Copy link
Collaborator

It is a bit annoying that such links aren't possible. On the other hand, it is probably OK to not have a link back, as all the other (external) link targets the project homepage refers to don't have back links either.

@nigelmegitt
Copy link
Collaborator Author

I guess one easy but less elegant fix is to link to a non-relative URL and label it as the public built one, and describe where the locally built one will end up with a path string that isn't a link. What do you think @spoeschel ?

@spoeschel
Copy link
Collaborator

This sounds good.

describe where the locally built one will end up with a path string that isn't a link

Would this description be on a separate page, as part of the Sphinx documentation? If so, at least within that page it would be possible to (also) add a link that references the parent folder - only the toctree directive is restricted in this aspect.

Or would it maybe be enough to just add the local link back to near the top of index.rst?

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

No branches or pull requests

2 participants