You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am planning to organise a few interview style meetups with Chris S (and other developers across the stack) to assist with updates for documenting the jupyter-book software stack and design.
I am planning to record these sessions (and make them available) so we don't all have to login at the same time etc. in the various timezones around the world -- however I would like to collect some questions for each interview topic. If you could add some below -- that would be great.
Developers: Also if you're willing to be interviewed I would love to setup a time to talk about your part of the jupyter-book stack. (Perhaps thebe, mystjs etc.)
Next Topic:
Topic 1: Deep dive into Parsing: myst-parser, markdown-it-py and MyST Specification (with @chrisjsewell)
Update 01st March 2022 I think this is a good first topic as there is a lot of ongoing work around mystjs and developing myst as a specification that might benefit from this first.
Update 07th April 2022 Scheduled for 08th April 2022
Overview of how the parser ecosystem works
What does the parser depend on (i.e. markdown-it-py) to tokenise and prepare ast
How does markdown-it-py work and what work is it responsible for?
Which ast objects can myst-parser interface with (i.e. sphinx etc.) (i.e. transforms applied at parsing)
What repositories form the parser stack (i.e. dependencies of myst-parser?
How does the parser layer interface with docutils, sphinx, myst-nb
What translation work is done by the parsing layer (i.e. links?)
Topic 2: Overview of Jupyter Book Software Stack (with @chrisjsewell)
Topic 3: Deep dive into myst-nb and extensions (with @chrisjsewell)
Topic 4: TBA
The text was updated successfully, but these errors were encountered:
I am planning to organise a few
interview
style meetups withChris S
(and other developers across the stack) to assist with updates for documenting thejupyter-book
software stack and design.I am planning to record these sessions (and make them available) so we don't all have to login at the same time etc. in the various
timezones
around the world -- however I would like to collect some questions for each interview topic. If you could add some below -- that would be great.Developers: Also if you're willing to be interviewed I would love to setup a time to talk about your part of the
jupyter-book
stack. (Perhapsthebe
,mystjs
etc.)Next Topic:
Topic 1: Deep dive into Parsing: myst-parser, markdown-it-py and MyST Specification (with @chrisjsewell)
Update 01st March 2022 I think this is a good first topic as there is a lot of ongoing work around
mystjs
and developingmyst
as a specification that might benefit from this first.Update 07th April 2022 Scheduled for 08th April 2022
parser
ecosystem worksparser
depend on (i.e. markdown-it-py) to tokenise and prepareast
markdown-it-py
work and what work is it responsible for?ast
objects canmyst-parser
interface with (i.e. sphinx etc.) (i.e. transforms applied at parsing)parser
stack (i.e. dependencies ofmyst-parser
?parser
layer interface withdocutils
,sphinx
,myst-nb
translation
work is done by theparsing
layer (i.e. links?)Topic 2: Overview of Jupyter Book Software Stack (with @chrisjsewell)
Topic 3: Deep dive into myst-nb and extensions (with @chrisjsewell)
Topic 4: TBA
The text was updated successfully, but these errors were encountered: