Open ljwolf opened 5 years ago
oh yeah and also this means that every workshop can get hosted at pysal.org
. So, for instance, see pysal.org/scipy2019-intermediate-gds
To bookify a workshop:
docs
in the root of the workshop.docs/content
. github.com/pysal/scipy2019-intermediate-gds
,
intro.md
file for that section./docs
folder. I'm still fuzzy on how to get the thebelab
integration working. I've read the directions on integrating with execution contexts, but I'm still fuzzy as to how to get this working. Could ask @choldgraf like we did for the @gdsbook?
Instructions for getting started on windows. If you are on Windows the approach we are using is based on: https://jupyter.org/jupyter-book/intro.html
I had been using the docs
folder in github.com/pysal/scipy2019-intermediate-gds, but it's OK to serve from the gh-book
branch if folks find that easier?
Looks amazing!
Hey all - this looks awesome :-)
just a quick note that if you try building a jupyter book on windows, please do leave feedback about what is hard/confusing/etc! Getting Ruby to work is a huge pain in the butt in my experience, and we're still trying to figure out the right way to guide people through it (hopefully in the future we can switch to Hugo, and this will make everybody's life much easier)
Hey all - this looks awesome :-)
just a quick note that if you try building a jupyter book on windows, please do leave feedback about what is hard/confusing/etc! Getting Ruby to work is a huge pain in the butt in my experience, and we're still trying to figure out the right way to guide people through it (hopefully in the future we can switch to Hugo, and this will make everybody's life much easier)
Hugo all the things ;->
oh yeah and also this means that every workshop can get hosted at
pysal.org
. So, for instance, seepysal.org/scipy2019-intermediate-gds
This Jupyter book is just amazing!!!
Hugo all the things ;->
first I have to learn Hugo (or find someone who knows it) :-)
In case it helps, this is the method we currently use to set up a book:
https://github.com/pysal/notebooks/blob/master/lib/build.py#L77
And below are the ones that build the TOC automatically. To be clear, this is for a very specific structure, but it might be helpful to write a TOC-builder from a more general folder of notebooks maybe?
many of our recent workshops link directly to a github repository where the source for the workshop is stored. However, @thedatalass correctly notes that this is very alienating for many users.
One thing I've looked into is making jupyter-books for workshop content. This has a few advantages.
The process involved in making jupyter-books out of our workshops will not be complicated. I propose that we do this at least for the first 5/10 workshops.