103
edits
Changes
Created page with "== Code4Lib 2016 Preconference Workshop Leaders Guide == Here is some information to help you make your Code4Lib 2016 Preconference Workshop a success. Short link to this pag..."
== Code4Lib 2016 Preconference Workshop Leaders Guide ==
Here is some information to help you make your Code4Lib 2016 Preconference Workshop a success.
Short link to this page: bit.ly/
=== Before the workshops ===
In the time leading up to Code4Lib 2016, please do the following:
* For all workshop leaders, please fill out our Code4Lib 2016 speakers profile form ASAP. Link: http://goo.gl/forms/JJDu1XlXHX This will display information about you on the Code4Lib 2016 Website.
* Help attendees prepare for your workshop by posting and emailing preparatory materials:
** Emails to those currently registered (lists will be emailed to workshop leaders separately)
** Link to your preparatory materials on the Code4Lib 2016 Website (for those who may have not registered yet so won't receive your email):
*** To do this, you can submit a pull request to the Code4Lib 2016 website on Github at https://github.com/code4lib/2016.code4lib.org
**** Navigate to _posts/ and find your session (will begin with '2016-03-0-7')
**** Please don't edit the structured data area, marked off with '---' above and below. Any content below the structured data can be edited as you desire!
*** Or, if you aren't comfortable submitting a pull request, you can send your preconference contact your changes or additions and we will take care of it for you
=== During the workshops ===
Please do the following during your workshop:
* Get a rough head count of attendees and share this with your Preconference contact or on site Code4Lib 2016 volunteer.
* Please remind people to only use the wifi with one device during the workshop.
We expect to update this page as new information is decided/emerges, so check back regularly and keep in touch with your preconference contacts.
And thank you again for taking part!
Here is some information to help you make your Code4Lib 2016 Preconference Workshop a success.
Short link to this page: bit.ly/
=== Before the workshops ===
In the time leading up to Code4Lib 2016, please do the following:
* For all workshop leaders, please fill out our Code4Lib 2016 speakers profile form ASAP. Link: http://goo.gl/forms/JJDu1XlXHX This will display information about you on the Code4Lib 2016 Website.
* Help attendees prepare for your workshop by posting and emailing preparatory materials:
** Emails to those currently registered (lists will be emailed to workshop leaders separately)
** Link to your preparatory materials on the Code4Lib 2016 Website (for those who may have not registered yet so won't receive your email):
*** To do this, you can submit a pull request to the Code4Lib 2016 website on Github at https://github.com/code4lib/2016.code4lib.org
**** Navigate to _posts/ and find your session (will begin with '2016-03-0-7')
**** Please don't edit the structured data area, marked off with '---' above and below. Any content below the structured data can be edited as you desire!
*** Or, if you aren't comfortable submitting a pull request, you can send your preconference contact your changes or additions and we will take care of it for you
=== During the workshops ===
Please do the following during your workshop:
* Get a rough head count of attendees and share this with your Preconference contact or on site Code4Lib 2016 volunteer.
* Please remind people to only use the wifi with one device during the workshop.
We expect to update this page as new information is decided/emerges, so check back regularly and keep in touch with your preconference contacts.
And thank you again for taking part!