create a site to show the curricula

[avallecam]

Before upgrading to alpha stage, we need to decide how episodes are going to be listed or organized.

The ideas to evaluate for this are:

• isolate early, middle, and late task episodes by nesting them in the website or separating them in different repos?
• locate this curricula website as an announcement site it in a learn post?

Here are two references:

• Carpentries lessons https://software-carpentry.org/lessons/
• Galaxy training https://training.galaxyproject.org/training-material/topics/covid19/

[avallecam]

@Bisaloo @rozeggo, this is the issue I referred to today, and we can discuss it around January.

[Bisaloo]

https://github.com/epiverse-trace/epiverse-trace.github.io/pull/157 is related to this issue.

[avallecam]

epiverse-trace/epiverse-trace.github.io#157 is related to this issue.

thank you, @Bisaloo

one additional and potentially useful reference for different lessons that are connected could be the Data Carpentry Ecology Curriculum with one Ecology Workshop Overview repo that connects them all, including general the setup instructions. Additionally, the section on lessons in Spanish.

I hope this split may in the future open the possibility of having different maintainers given the different topics of focused specialization.

Regarding the tags of the new repositories, should we give them topic-specific names, or use the early/middle/late words?

idea 1:

• early-outbreak-tutorial or tutorials-early-tasks
• middle-outbreak-tutorial or tutorials-middle-tasks
• late-outbreak-tutorial or tutorials-late-tasks

idea 2:

• read-clean-outbreak-tutorial or input-data-outbreak-tutorial
• real-time-outbreak-tutorial
• scenario-modelling-outbreak-tutorial

[avallecam]

To complement the evaluation of a repo split, the Carpentries Instructor Training repo is an example of a three-day workshop with all the content in only one repo.

This has the following structure:

• welcome
• chapters day 1
• end part 1
• chapters day 2
• break part 2
• chapters day 3
• wrapping up

[avallecam]

(EDITED) Some ideas regarding a preliminary evaluation of a split, using the references above (Ecology curricula and Instructors training), and in two dimensions: pedagogy and maintenance. These are phrased as ~pros/cons but could also be viewed as~ features that we comply with to carry on with the decision. One approach when deciding about technology-enhanced learning (TEL) tools is that the discipline-specific knowledge informs the practical pedagogy (technology) in practice.

split sites

pedagogy

• A more spread and divided learning associated with the data analysis workflow.
  • Each site will have its specific set of prerequisites.
  • This will facilitate associating specific tasks within the early/middle/late classification within a three-part process.
  • Although the early/middle/late categorization is a continuous gradient for packages, the tasks they work for are indeed more independent and connected by package inputs and outputs.
  • The idea of early/middle/late as a continuous gradient for packages may need clarification on their categorization for task-oriented tutorials.

maintenance

• Each piece will have its own loading time to generate previews and websites.
• Opportunity to have different maintainers focused on the content of different groups of tutorials.
• This must avoid replication or redundancy of shared content across repos, like setup updates.

ease to make derivatives

• A set of three tutorials may limit their forking to make local derivatives of the whole work.