July 1st, 2021

If you are joining the team video meeting, sign in below so we know who was here. Roll call:

  • Matthew McKay / Australian National University (ANU) / mmcky

  • Chris Sewell / EPFL / chrisjsewell

  • Steve Purves / Curvenote / stevejpurves

  • John Stachurski / ANU / jstac

  • Chris Holdgraf / 2i2c / choldgraf

  • Damián Avila / 2i2c / damianavila

  • Aakash Gude / ANU / AakashGfude

Reports, updates, and celebrations

This is a place to make announcements (without a need for discussion), short updates about what you’ve been up to, and shout-outs to contributors! We’ll read through these at the beginning of the meeting.

QuantEcon / ANU

  • QuantEcon: 4/5 Projects running Jupyter Book (remaining: julia)

  • ANU Team: Working on Support for Individual Page PDF (via LaTeX) generation (Lead: @mmcky)

    • Chris H notes that we should include updates about QuantEcon lectures conversion etc

    • @mmcky to add links to executable books gallery to QuantEcon jupyter-book powered projects

Chris S.

Recent work

  • Released sphinx-external-toc and integrated in Jupyter-Book

    • Removes a lot of code from jupyter-book 😄, moving towards JB just being a thin wrapper for sphinx-extensions (last part is basically the _config.yml)

    • Bit of a balancing act between; ease of use/understandanding, having a clear schema, having all the functionality of sphinx toctrees

    • Integration in JB also includes addition of “pluggable” CLI

  • Released markdown-it-py v1.0, i.e. fully stable

  • Released myst-parser v0.15.0, with sphinx v4 support

    • Should be moving all repositories to sphinx v4

  • Released rst-to-myst v0.3

    • Facile conversion of RST to MyST Markdown for a whole project

    • Utilises mdformat + mdformat-myst to create the Markdown from markdown-it tokens

    • Still working on mdformat-myst, but this essentially allows round trips Markdown text -> markdown-it tokens -> Markdown text. Could potentially be used for e.g. modifying links in downloadable notebooks

  • Created markdown-it-plugin-template; template repository with best practices for TypeScript library

Intended work

  • Update MyST VS Code extension to use new markdown-it plugins

  • Create sphinx-design: An iteration on sphinx-panels, but with the benefit of hindsight, and to more closely follow aspects of Materials Design and Material-UI

    • class names that do not clash with sphinx ones (i.e. container)

    • easier to set principle colors and width defaults

  • Either in myst-parser or sphinx-design have nice way to generate stylised post-header banners, with e.g. author, date, read time (see https://github.com/executablebooks/MyST-Parser/issues/372)

  • Improvements to myst-nb (+ jupyter-cache)

    • Been gradually working on it, but lot of interconnected parts 😬

    • Revise the AST and transforms (post-transform -> transform)

    • Drop nbconvert, jupyter-sphinx dependencies

    • Better support for Markdown code output

    • Better support for “multi-level” configuration (cell level > notebook level > conf.py level)

    • Improve notebook execution and (maybe) drop auto mode in favour of cache

      • Support for dynamic kernel names

    • How to handle glue; ideally in a kernel agnostic manner, possily with the new substitution syntax

    • Plugin CLI in jupyter-book for notebook execution


  • Would like to:

    • meet the team

    • hear about thoughts on Thebelab as I’m prepping to do some work there

Berkeley team

  • :wave: to Damian, onboarding etc

  • Damian is playing around with the MyST parser and learning how it is structured, experimenting with a Nikola implementation of the parser.

  • Chris is going to focus more of his time on team documentation, tool documentation for both users and developers, etc.

Agenda items

Didn’t get to the following items

John S:

  • Hiring casual RAs?

Chris H:

  • Communicating the work we’re doing - blog posts, tweets, etc? @executablebooks handle?

  • Coordinating around deliverables, workstreams, requests for reviews, etc?