Outline of hackweek train-the-trainer module content #49
Conversation
docs/overview.md
Outdated
There was a problem hiding this comment.
I suggest a short opening or admonition to this page to highlight the website purpose (I particularly like this sentence you wrote: Professionalizing Short-Format Training "the rigor of Formal Higher Education into our hackweeks, while maintaining our need for flexibility and creativity) Maybe:
```{important}
The purpose of this hackweek guidebook is to professionalize Short-Format Training with the rigor of Formal Higher Education for a successful and engaging learning experience. To that end, this guidebook is written for event organizers who complete 5 training modules in advance of a week-long event.
```
There was a problem hiding this comment.
For simplicity we could add a separate “History” page to keep each page relatively short
|
|
||
| After completing this module, tutorial leads will: | ||
|
|
||
| * create hackweek [learning objectives](https://www.sciencedirect.com/topics/social-sciences/learning-objective) using Bloom's Taxonomy |
There was a problem hiding this comment.
Doesn't need to happen in this PR, but given the more formal content, we can add a glossary page which I think is nice for things like “learning outcome”, “Short-Format Training”, “Bloom’s Taxonomy” (http://book-template.hackweek.io/reference/glossary.html)
docs/_toc.yml
Outdated
| - caption: Reference | ||
| chapters: | ||
| - file: participant-selection |
docs/_toc.yml
Outdated
| @@ -25,7 +28,10 @@ parts: | |||
| - caption: Learning Culture | |||
| chapters: | |||
| - file: culture/index | |||
| sections: | |||
| - file: culture/psychological-safety | |||
There was a problem hiding this comment.
currently missing this page
This PR includes draft learning objectives for each of the 5 hackweek organizer team training modules I have proposed. The learning objectives are located in the index.md file of each of the sections (Tutorials, Projects, Technology, Strategy, Culture).