-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added horizontal breakpoints to each secondary header + updated readme
- Loading branch information
Showing
29 changed files
with
201 additions
and
127 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
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
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
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 |
---|---|---|
|
@@ -29,10 +29,9 @@ software or tools. We only mention certain software products to | |
illustrate our points. We separate the guidelines along the timeline of | ||
before, during, and after the training. | ||
|
||
--- | ||
|
||
## Before the Training | ||
|
||
--- | ||
|
||
A large part of the trainer’s work will already be done in preparation | ||
for any training event. Here, we list some points that should be considered when preparing to provide a well-received training event. | ||
|
@@ -193,10 +192,9 @@ everyone. A good introduction is given in “[Ten simple rules for making | |
training materials | ||
FAIR](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1007854)”. | ||
|
||
--- | ||
|
||
## During the Training | ||
|
||
--- | ||
|
||
### Arrival | ||
Before the first session of your training event, you should | ||
|
@@ -330,10 +328,10 @@ training in the future. Do try to ensure that the feedback can be | |
anonymous and that the questions highlight points of improvement to | ||
enable you/the team to provide an even better experience the next time. | ||
|
||
--- | ||
|
||
## After the Training | ||
|
||
--- | ||
|
||
Shortly after the event, you should **meet with all trainers** involved | ||
and **gather their feedback**. Collect points that should be improved | ||
|
@@ -354,7 +352,8 @@ benefit from the work you already provided. If you do so, make sure to | |
state under what license you provide your work. We suggest a permissive | ||
license such as [CC BY](https://creativecommons.org/licenses/by/4.0/), or „CC 0“. | ||
|
||
## Get Help | ||
|
||
--- | ||
|
||
## Get Help | ||
If you have any further questions about the management and analysis of your microbial research data, please contact us: [[email protected]](mailto:[email protected]) (by emailing us you agree to the privacy policy on our website: [Contact](https://nfdi4microbiota.de/contact-form/)) |
Oops, something went wrong.