knitr::opts_chunk$set( collapse = TRUE, comment = "#>" )
Authors:
Vince Carey^[Channing Division of Network Medicine, Brigham and Women's Hospital],
Another Author^[Another Institution].
Last modified: 1 Nov, 2020.
This document is a technical illustration of how workshop documents are authored and rendered. The content of this document will change completely as the workshop content is specified.
Describe how students will be expected to participate in the workshop.
List any R / Bioconductor packages that will be explicitly covered.
An example for a 45-minute workshop:
| Activity | Time | |------------------------------|------| | Brief intro to R/Rstudio | 10m | | Biological context | 10m | | Packages to be used | 10m | | Analytical approach to the question | 15m | | Simple exercises | 10m | | Review | 5m |
List "big picture" student-centered workshop goals and learning objectives. Learning goals and objectives are related, but not the same thing. These goals and objectives will help some people to decide whether to attend the conference for training purposes, so please make these as precise and accurate as possible.
Learning goals are high-level descriptions of what participants will learn and be able to do after the workshop is over. Learning objectives, on the other hand, describe in very specific and measurable terms specific skills or knowledge attained. The Bloom's Taxonomy may be a useful framework for defining and describing your goals and objectives, although there are others.
Some examples:
Divide the workshop into sections (## A Section
). Include
fully-evaluated R code chunks. Develop exercises and solutions, and
anticipate that your audience will walk through the code with you, or
work on the code idependently -- do not be too ambitious in the
material that you present.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.