about the content in learn tab

[avallecam]

(...) Flagging that this change will likely be made obsolete by #157 though.

I expect this content to be part of the intro to the lesson materials instead. What do you think?

Originally posted by @Bisaloo in https://github.com/epiverse-trace/epiverse-trace.github.io/issues/164#issuecomment-1893616115

[Bisaloo]

Yes, I agree. Sounds like a good plan :+1:

[avallecam]

brief issue to reply to this question.

I agree, that the structure of the workshop website is now within the lesson material structure of the workbench.

• How to participate? - (may be variable, depending on the event)
• What will you learn? - general learning outcomes can be more explicitly placed in the summary side
• Who is this training for? - in profiles tab
• What is not included in this training? - this can also be placed in the prereq section within the summary tab.
• Duration - (may be variable, depending on the event)
• Program - in the instructors view tab
• Materials you will need - in the setup section
• Materials we used - (may be variable depending on the event)
• Any questions? - in the learner view index page

For the event-dependent information, we can use a workshop page, relying on the workshop-template, like in the following example.

This workshop page should include:

• how to book a place / how to join a waiting list / how to cancel
• session information:
  • from xx:xx am to yy:yy am
  • session type: in-person or remote
  • venue
• general info (briefly summarizing bullet points or a subset of them for:)
  • aim
  • content
  • target audience
  • prerequisites / code of conduct
  • learning outcomes

My follow-up question is: when this page may be needed, could the workshop page live in the epiverse-trace repository? this would look like a gh-page deployed from a new repository https://epiverse-trace.github.io/2024-02-12-git-training, but not indexed within the main page. an alternative could also be to host it from the instructor's repository, as the carpentries seem to do, possibly because of potential overloading of event repos.

[avallecam]

Yes, I agree. Sounds like a good plan 👍

actually, the question in the first comment is yours, hehe. my reply is in the following comment

[Bisaloo]

My follow-up question is: when this page may be needed, could the workshop page live in the epiverse-trace repository? this would look like a gh-page deployed from a new repository https://epiverse-trace.github.io/2024-02-12-git-training, but not indexed within the main page. an alternative could also be to host it from the instructor's repository, as the carpentries seem to do, possibly because of potential overloading of event repos.

Yes, that's possible.

It may be easier from a maintenance point of view to have all this content in the main tutorials repo, which then dispatches to tutorials-early, tutorials-middle and tutorials-late. Is this not an option?

Happy to follow your final recommendation though. Both options are feasible from a technical point of view.

[avallecam]

Good to know that they are feasible.

It may be easier from a maintenance point of view to have all this content in the main tutorials repo, which then dispatches to tutorials-early, tutorials-middle and tutorials-late. Is this not an option?

Yes, that is the approach for the general info and intro episode.

To clarify, here I am visualizing a "workshop page" apart from any "lesson material":

• the "workshop page" will be event-specific (more focused on how to book, and session information -from, to, venue-), while
• the "lesson material" will try to be as static as possible (all the workbench repos).

For that rationale, the "workshop page" may probably not be within the workbench repo, although I'll though about it when required.

With respect to the aim of the issue raised, I'll use the info registered here to display the mapped info to move it to the corresponding git repo. I'll close this and site it in the git repo in a different issue.