-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Including Presenting and Developing sections
- Loading branch information
1 parent
540fdf0
commit 257c858
Showing
27 changed files
with
1,290 additions
and
400 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
# Presentation | ||
# Présentation {#presenter-fr} | ||
|
||
*Nous sommes en train d'ajouter des modifications à cette page. Veuillez revenir plus tard.* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Développer | ||
|
||
Nous sommes en train d’ajouter des modifications à cette page. Veuillez revenir plus tard. |
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
# Presentation {#presentation-en} | ||
|
||
*We are adding modifications to this page. We kindly ask you to come back later.* | ||
|
||
The following recommendations have been written with critical thinking and with the objective to improve the delivery of the content to workshop participants. | ||
|
||
We propose guidelines based on evidence-based strategies for teaching and learning. | ||
|
||
Even though a few aspects might be basic to you, we ask you to *carefully* read them. | ||
|
||
## Workshop structure | ||
|
||
In average, workshops last 4 hours (including eventual breaks), with some variation depending on the length of the workshop content and with its complexity. | ||
|
||
During both remote and in-person workshop contexts, breaks of 5 to 10 minutes (each) should be provided to allow participants and presenters to take a short pause. | ||
|
||
See the proposed format below for the workshop structure: | ||
|
||
*Include table.* | ||
|
||
### Workshop presenter guidelines | ||
|
||
1. Instructors should consider themselves students during the learning process, and be thoughtful on their method of delivery and communication, and how it affects student learning; | ||
|
||
2. Instructors must come to workshop prepared to instruct the workshop material, as well as to respond to relevant questions related to the workshop; | ||
|
||
3. Instructors should **not** only read the presentation during a workshop; | ||
|
||
4. *Continue...* | ||
|
||
### Workshop assistant guidelines | ||
|
||
1. *Continue...* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Developing {#developing-en} | ||
|
||
## Guidelines | ||
|
||
Because we would like workshop participants to focus in what is being instructed and not in eventual issues with style, grammar, punctuation and structural issues, we provide this short reference guide to help developers create and modify the content of workshops. | ||
|
||
### Structural rules | ||
|
||
1. Do not allow the content of slides to overflow the screen. | ||
|
||
2. The code used to generate an outcome (figure or calculation), should correspond to the code being displayed. *Include example*. | ||
|
||
3. Use backticks ` whenever you mention a function, an object or a package in your text. | ||
|
||
4. Use three backticks to separate code chunks from prose. | ||
|
||
5. *Continue...* | ||
|
||
### Content changes | ||
|
||
#### Grammar and style | ||
|
||
1. Pay attention to punctuation, spelling, grammar, and capitals. | ||
|
||
2. Avoid unnecessary abbreviation (e.g. prefer *do not* instead of *don't*;). | ||
|
||
3. Avoid very long phrases. | ||
|
||
4. *Continue...* | ||
|
||
#### | ||
|
||
1. Be coherent. | ||
|
||
## Exercise examples | ||
|
||
*Compile and produce examples from evidence-based learning modes and effective strategies to deliver remote workshops to participants.* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.