How to maintain separate repository with notebooks/binder/etc.

[klieret]

There is a separate repository (https://github.com/hsf-training/hsf_matplotlib_notebooks), soon to be transferred to this organization that contains pre-filled notebooks.

How do we maintain them in the future?

[amangoel185]

There might be similar workflows in The Carpentries which we could look into!

[amanmdesai]

I just had a thought about this issue:

We can perhaps use some tool that converts our markdown file into jupyter-notebook content?

For instance, this package converts jupyter notebook to markdown.
We could modify it to suit our requirement (markdown to jupyter notebook conversion)

[klieret]

nbonvert is pretty great :)

I'm more thinking of going the other way: If we want to have a completely pre-filled notebook (not sure if we want to, see survey picture below), then I think we should use Jupyter notebooks and build a website from them using jupyter book.

Maybe with the amount of code that's flung around in matplotlib the survey result doesn't really apply though (because that would be a lot of typing...)

[amanmdesai]

Thats sounds good.

The analysis-essentials repo's advanced python module uses jupyter notebooks and website is generated from the notebooks for this particular topic (as far as I understand). We can use a similar kind of workflow maybe.

Regarding survey: I think that having pre-filled notebooks is better as that saves time.
(Also it may be possible to prepare an extra semi-filled notebook with some exercises [with hints] )

[GuillermoFidalgo]

In terms of having pre-filled notebooks I, it all depends on the workflow used.
If we are thinking about active training then having pre-filled notebooks will take away interest or motivation from students to pay attention.
If we are thinking of passive learning when students are reading the notes on their own, then prefilled notebooks provide an interactive environment with examples.

I believe we can keep the pre-filled notebooks if students ever want to see some solutions.

[stale]

This issue or pull request has been automatically marked as stale because it has not had recent activity. Please manually close it, if it is no longer relevant, or ask for help or support to help getting it unstuck. Let me bring this to the attention of @klieret @wdconinc @michmx for now.