Communicate the Life cycle of Tutorials to learners

[avallecam]

Lessons in the tutorials repo are following an iterative development life cycle (ref). Currently in pre-alpha stage.

This stage of development is labelled into three sections:

• Topic tags in the About section on GitHub (location) (following workbench template guidelines)
• Lifecycle badges in README: lifecycle experimental and repo status WIP (location) (following dev stages of open source software)
• Lesson lifecycle in the upper left corner of the URL lesson (location) (defined in the config.yaml of the repo)

These could be visible to competent practitioners in open software development, but probably not as much for our learner personas.

We can complement them with more visual cues:

• One callout in the Front page Summary section: We can add one callout box (see list of variations) explaining briefly the current dev-stage of the tutorials, after the Summary and before the Software Setup of the current front page.
• Share about the Communication channels for these tutorials: As part of the design features for this repo, we want to guide learners to communicate via the Discussions tab. We can add this to the same callout box above with links to the Support and Contributing files as more visible reminders on the front page. (For an example of this, refer to a previous tutorial)

Happy to read your thoughts and alternatives to this.

[Bisaloo]

Relevant: I've pulled the latest changes from carpentries/varnish@main and the lesson lifecycle icon is now much more prominent:

[avallecam]

Thank you for that update! That is a good emphasis.

Should we update the link? It currently redirects to the CDH, which is explicit and informative for lesson developers (the intended audience of the CDH), but not as direct in the message as the section on iterative development.

[avallecam]

I think we can wait for an update in their side as notified in this carpentries/varnish#41

[avallecam]

closing. Stage now visible in from learn page https://epiverse-trace.github.io/learn.html and with an appropriate visibility on tutorial heading