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
move to GitHub pages #3884
move to GitHub pages #3884
Conversation
- name: Build and deploy to GitHub Pages 🏗️ 🚀 | ||
working-directory: docs | ||
run: | | ||
mkdocs gh-deploy --force --strict |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sure there's no warnings when building the docs, or the workflow will fail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
e.g. linking documents which don't exist (many of those previously)
this is also ready for review/merge. |
|
||
## Contributing | ||
|
||
We :heart: contributions to Valhalla. They could be non-technical, e.g. translations into other languages via [Transifex](https://www.transifex.com/valhalla/valhalla-phrases/locales-en-us-json--transifex/) or documentation improvements, or technical ones like bug fixes or feature implementations. It's important to open an issue before setting out to work on a PR. | ||
|
||
Ideally, get familiar with our [Contribution guidelines](./CONTRIBUTING.md) first. | ||
Ideally, get familiar with our [Contribution guidelines](https://github.com/valhalla/valhalla/blob/master/CONTRIBUTING.md) first. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some are docs links like building
above but this one and the run routes readme link to markdown on the master branch. this is a bit confusing to me. is it because docs generation doesn't docs-ify those? or should these markdown links be github.io docs-ified links?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, it can't link them relatively because it doesn't have access to anything outside the ./docs/docs
folder, see its branch: https://github.com/valhalla/valhalla/tree/gh-pages/. Symlinking wouldn't work here either, then the github.com version wouldn't find the right doc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or well, with symlinking we could put the absolute URL of the GH Pages version. I don't really mind either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh i just wondered if the make docs would turn the markdown into html to be rendered nicely without the built in github viewer but it seems like not? or maybe not by default? i am definitely not up to date on how the docs are generated. like why doesnt https://valhalla.github.io/valhalla/contributing
get generated from the markdown? oh i see we have to change it in the yaml below and if we did that then we could have a nice html version of the markdown?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the make docs would turn the markdown into html to be rendered nicely without the built in github viewer
Oh yes, sure it does. If not, we couldn't verify locally. The "github viewer" doesn't do anything at all actually, other than pointing the URL to the right path on their server, the rest is all mkdocs: https://github.com/valhalla/valhalla/blob/gh-pages/index.html.
Again, it cannot view anything that's outside of ./docs/docs
and CONTRIBUTING.md is in master's root. If we'd like it in the docs HTML version, we'd have to symlink as we did with the root README. We can do that and then put the absolute URL of the docs version, so when someone clicks it on github.com it'll forward to github.io.
Hi @nilsnolde, I can look into this and see if it's associated with my account. I'm sure there are sites linking to various pages on valhalla.readthedocs.io, so it would be best to set up redirects. Here's one person's suggestion on how to do so: https://stackoverflow.com/a/69928404 |
Ah that's a very good point! But man, my motivation getting involved with Sphinx ever again is pretty low 😅 |
I can't access config on readthedocs. I contacted support and they say that @kevinkreiser is the project owner for valhalla.readthedocs.io Kevin, can you set up some redirects? Or you can share access with my drewda account and I can try to help. |
Ah sorry @drewda , I thought I remembered the account was on your name. Then we’ll figure it out, thanks:) |
@nilsnolde np! I think my vague memories of setting this up are probably the formatting work in #1697 |
ok ive done the redirect by making a repo and immediately archiving it. now if you try to go to: https://valhalla.readthedocs.io you will be redirected to: https://valhalla.github.io/valhalla |
./docs/docs
, which is necessary when we want to keep themkdocs.yml
in thedocs
directory, which I'd prefer@drewda would you mind removing the docs from readthedocs.io once this is merged? Then there won't be any ambiguity with a stale documentation still being live there.