Jeremy announced recently that we added Jupyter notebook automation into fast_template. We also added similar automation for word docs.
UPDATE: The new repo is up here: https://github.com/fastai/fastpages
We would love to your input, and have you try it out! Please give it a go!
Bad News: We recently took all the automation out. Because we found the extra setup steps required to make this work properly (creating an SSH key, adding it to your secrets, etc may be too cumbersome and confusing for beginners).
Good News: We are rebuilding a “power user” version of fast_template, called fastpages with all of the Automation and more exciting features. We are building it from the ground up to be automated and modular enough so you can take the automation to any other Jekyll theme of your choice. The reason for doing this is it will allow us to have the following features:
- Automatic Jupyter / Word doc to blog post conversion without making your local copy’s master branch out of sync (which would otherwise require you to keep pulling before committing).
- More transparent build status of your GitHub pages - you will get to see the full logs
- Flexibility to use whatever plugins, gems, etc. that you want even if they aren’t whitelisted by GitHub Pages.
- Jupyter blog posts retain interactivity where possible (ex: Altair Charts).
- Additional CI and Tests that will help both maintainers and users
- Modularity such that you can take this automation to a different Pages theme, including any third party theme so you can customize the look and feel of your blog but still retain automated Jupyter and Word doc to blog post conversion.
This is an open thread to discuss the development of fastpages
- We will probably stick with Jekyll, even there are more robust static site generators like Gatsby, in order to leverage the strengths of nbdev and the knowledge of this community.
Some preliminary ideas of things to discuss (Feel free to discuss anything else):
- What plugins do we want ( might be good for testing purposes to know )
- Are there any features that would be particularly useful for fastai students?
- What CSS to include? Perhaps we drop
Primerand use something more lightweight that doesn’t clobber other themes. We could, for example, borrow some of the css you are using for the docs sites that allow for the useful things like callouts and such. ( I think it is defined here).
- Ideas for tests: The only kind of tests I can think of is to kick off a jekyll build (without committing the build) and see if that provides an error - this might help catch errors on PRs to the template.