[NB: no tag or topic for JupyterBook? Am I in the right place here?]
Hi! I’m thinking about migrating https://edu.oggm.org from sphinx+readthedocs to JupyterBook+ghpages.
I have two questions which I hope are not too trivial:
I’d like some of the widely shared links to redirect to the new jupyterbook equivalents. E.g. https://edu.oggm.org/en/latest/explorer.html -> whatever jupyterbook chose instead. I think I’ll have to fiddle around manually in the _build html files to do that, right? But it won’t be a problem or really difficult, will it?
I really like the multilingual capability of sphinx - although we haven’t translated much of it yet, https://edu.oggm.org is technically available in other languages already. Does jupyterbook support localization like readthedocs does?
Hi! I wonder if it would be useful to connect with The Turing Way community? We had to handle some redirects and are also trying to provide multiple translations of the content as well. All built with Jupyter Book, though we publish with Netlify rather than GitHub Pages.
Just out of curiosity: Would you be willing to share some of the reasons for changing?
What are you missing on Sphinx+RTD that’s there on JupyterBook+ghpages?
BTW, the newest generation of JupyterBook also uses Sphinx, but I guess that’s an implementation detail.
I like the style of juptyter book (although I guess I could just switch to Sphinx Book Theme for that)
We’d like to use jupyter notebooks as content as well. Although I assume that there are sphinx tools for that, jupyter-book is just so… easy and seamless. I also really enjoy the automated stuff like the automatic links to mybinder
Our notebooks (which are currently only linked as “tutorials”, i.e. not rendered) need to run on rather complex python environments: I find it a real pain that we can’t use containers on RDT, and need to reinstall the 20+ packages via conda each time we will build the docs. With our own CI + ghpages we can use our containerized envs and resources to actually build the website instead of relying on RTD for the build…
The advantage here is that you are not limited to Binder links, you can link to anything you want in any way you want.
OK, that’s a really good point.
But this really doesn’t have anything to do with Jupyter Book, it’s all about RTD vs ghpages.
Installing stuff with conda on RTD can take a really long time, and the total runtime of your build is limited (last time I checked it was 15 minutes for non-paying accounts), so it might not be feasible.
But even if you switch to ghpages (which seems to make a lot of sense), you can still decide to use “plain” Sphinx.
Running Sphinx on CI and pushing the generated HTML files to ghpages should be trivial, but I guess it would be very nice to have multiple versions/languages there, which is for sure far from trivial. Sadly, I don’t know of a solution for that, I hope you’ll find something!
Thanks for all the tips! After giving it some thought, I think we’ll migrate the notebook only part to a jupyter-book page and leave the rest as is (maybe with some efforts to make the site look a bit nicer).