I am working on an "extension" of the gh_workflow episode where the workflow for gitlab pages is also shown. This is also partially inspired by the current situation in the testing repository, where the gitlab way is also shown.
I am doing this because of two reasons:
- many of the participants to the workshop I'm planning will have likely access to a gitlab server
- presenting alternatives might make things more complicated, but it improves freedom, and education should foster freedom, besides "basic literacy". The tabs approach allows to present alternatives in a way that does not reduce clarity for the basics (the "main" track) while letting curious people to explore alternatives with a simple click.
But it's also true that
- point 1 might not apply to the average coderefinery workshop participant
- I see that gitlab used to be more present in this lesson (along with RTD, for example) and that recently, I guess for simplicity, github pages has been chosen. After all, the first week runs on GitHub, so...
- adding tabs/tracks does increase the maintenance workload
Is there some thought/wisdom/common policy about this in general? I did not find anything immediately in the Lesson Contribution guide, except for a general call to conciseness and need to limit the length.
I am working on an "extension" of the gh_workflow episode where the workflow for gitlab pages is also shown. This is also partially inspired by the current situation in the testing repository, where the gitlab way is also shown.
I am doing this because of two reasons:
But it's also true that
Is there some thought/wisdom/common policy about this in general? I did not find anything immediately in the Lesson Contribution guide, except for a general call to conciseness and need to limit the length.