Think abt timing and hands-on process

[stephwright]

Think about how to address the following feedback:

• pre-work to understand concepts before jumping into hands-on workshop
• instruction w/ more specific tasks w/ pre-built items so everyone is doing the same thing i.e. get a hyperlink on the webpage
• could make a full day- 1/2 same as today's 1st half, if people want more opt to stay for afternoon
• live coding the process rather than slides (sugg from @gallingerj)
• demo before letting us try or use it
  would have liked table-sized groups after the break - hard to keep up from the back of the room

[gallingerj]

In particular, I think doing a pull request together once would have been helpful (i.e. learners follow along). There were folks creating weird branches to pull from and other bizarre methods of trying to do the pull request. I addressed these from table to table but I think it was a common confusion.

Another instruction point would be to point out the repo name and folder structure to help folks navigate better, i.e. click on "friendly-github" to navigate to the repo homepage on the "mozillascience" account.