Draft: Organise notebooks into website content

[alanmlewis]

Hi Andrew and @m-rivera , this is my first go at organising the notebooks into something visible on the website. They will need a lot of standardisation; we'll need to think about the best way to approach that. This PR shouldn't be merged until at least some progress on that is made, although I think I'm happy to publish with some TODO stuff still listed.

Also, I have a couple of specific questions:

1. Is there a way to get Jupyter book to essentially ignore code errors and continue anyway? There's a few places where people have written debugging exercises, but then nothing later in the notebook actually runs.
2. How do we want people to be able to contribute to this further? After we've done some standardisation, we'll want them to update the standardised version, not the original. I guess we'll just need some instructions on how to pull the updated version to their fork and then where to find their notebook that they've worked on.

[arm61]

For (1), I have updated the yml.

[arm61]

I guess we'll just need some instructions on how to pull the updated version to their fork and then where to find their notebook that they've worked on

Yes.

[arm61]

Looks like you might have forgotten to clear all outputs?

[m-rivera]

Hi all!

Just working on this now. A couple of questions:

• I see that we copied all the notebooks instead of git mv, which loses track of the authorship. I guess the original authors can still point to their first commits to prove their contribution. Are we ok with that or shall I try to do some repo management to recover the full history (preserving @alanmlewis 's new edits)?
• Have we got the ordered table of lessons that we allocated in York (or equivalently, is that what is in _toc.yml)?
• Shall we use GitHub Issues to call dibs on any lessons we're working on at the moment?

[alanmlewis]

Hi @m-rivera,

• Yes, sorry about that. I didn't want to lose the originals, because we will have to take some stuff out in order to standardise, but that's lost the authorship track. I think it's probably OK - as you say people can still point to the initial commits (and make future commits if they want!).
• Yes, that's what's in _toc.yml.
• Yes, I'll create issues for each lesson now.

I'll probably do some of this this afternoon and tomorrow - please let me know what you're working on so I know what to avoid!