The teach site is currently serving two target groups: teachers and students. It might be useful to have two distinct sites teach and learn, for teachers and students respectively. The former should contain the "complete" collection (including teacher-specific instructions, etc.), while the latter should be a reduced version containing only what's useful for the students.
Ideally, the learn site's script definition should be a function of the teach site's definition + markers. This might require for the marker system to be expanded to allow for marker exclusions. For instance, an article some-article.[gym,teachers].md should be included in the gym script for the teach site, but not for the learn site.
It would also be useful for each article on the teach site to provide a Go to Learn button, which changes to that same article in the learn site. Requirements for this would include:
Article (i.e. component in article) contains logic to decide whether the button should be shown (when on teach) or hidden (when on learn).
Article contains logic to decide not to show the button on teacher-only sites.
The
teachsite is currently serving two target groups: teachers and students. It might be useful to have two distinct sitesteachandlearn, for teachers and students respectively. The former should contain the "complete" collection (including teacher-specific instructions, etc.), while the latter should be a reduced version containing only what's useful for the students.Ideally, the
learnsite's script definition should be a function of theteachsite's definition + markers. This might require for the marker system to be expanded to allow for marker exclusions. For instance, an articlesome-article.[gym,teachers].mdshould be included in thegymscript for theteachsite, but not for thelearnsite.It would also be useful for each article on the
teachsite to provide aGo to Learnbutton, which changes to that same article in thelearnsite. Requirements for this would include:teach) or hidden (when onlearn).