Building Tools for Instructor Training Workshops
Wherein we talk about building tools to help instruct instructors learning how to instruct. Got that? No? Me neither. As a fairly newly minted instructor-trainer, one of my internal gripes about preparation was the need to create the Etherpad training template which serves as a shared note-taking space and workbook for the class.
Preparing this etherpad involves either editing an old text file which isn’t maintained as part of the normal lesson maintenance process (as that sort of maintenance would be tedious in the extreme) or laboriously copying and typesetting exercises from their beautiful (but non-translatable) html form into the limited number of styles allowed on the Etherpad. As I was getting ready to teach in July, the amazing Instructor Training Maintainers team were in the middle of the June release – and every time I had prepared the document, another exercise would be improved. This wonderful process of improvement, in the moment, was more than a little frustrating.
Thus as a techie, I built a tool to solve this problem for me: The Etherpad Template source which very carefully asks Jekyll to combine all lesson pages into one giant page of doom, and then very carefully removes and restyles elements through dynamic jQuery calls to make a framework for our new instructors to take notes within. I would be delighted if my fellow instructor-training colleagues would find this tool useful for their own training sessions.
Demonstrating the Tool
My user story:
As a lead instructor, I want to copy a ready-to-go notes document for my upcoming workshop into a shared document of my choice so that I can know that the lessons in my shared document reflect the lessons I am teaching from.
I’ve used this tool in three workshops.
The most successful use was in my Train-the-trainer workshop shared document:
The tool takes:
and turns it into:
I also was in a great rush preparing for Resbaz Sydney and so I used the tool with little customisation, to much more mixed results to create a Python workshop shared document. (Thus me raising the issue on styles for how folk use the tool.)
Students took shared notes and this export to google docs went adequately well. Though the SVG transfer process was problematic and I ran out of time to solve it properly.
Unfortunately, buoyed by my success with Python, I didn’t test the SQL shared document well enough and ended up with random blocks of data throughout:
While correcting this is important so I can use my tool for my own future workshops, we now have the opportunity to generalise from these examples to fit the needs of the community.
Starting a Conversation
I’m currently working on generalising the tool to all lessons. Comments reflecting on how you use shared documents (Etherpad/google Docs/any other?) in your workshops are invited to join the conversation on Github.
- What would you want the see the tool copy over?
- What should the tool omit? (And is it currently omitting the right stuff)
- Is there any pro-forma language we should or should not copy?
- How do you use shared documents in your workshops? And how could this tool support your efforts?
Dialogue & Discussion
Comments must follow our Code of Conduct.