Background

=========

Stephanie and anyone else, please fix any incorrect GitHub and modularity thinking here, thanks.

As a community, we are creating a knowledge pool of modular course materials. Modular here means, creating discrete pieces of content, each explaining what, how, and why for a task. The learner might be a contributor learning or reminding how to do the task; or the learner might be a user taking a full SRE course. The same content can be used in both cases, but placed into a context specific for the different learner type. This content therefore is more than a Markdown file, it has inline or metadata (labels, etc.) that means it can be organized to appear in multiple learning pathways.

These multiple learning pathways currently are: SRE Learners, Open Source Developers, Project Contributors, and Data Scientists and Data Engineers.

So if combining the pool with the number of learning path options, it could be four separate learning paths with e.g. twelve modules per path. Those modules would comprise existing modular content, combined with content specific to the module that shapes the relationship to the learner persona. An example of a single module might be, "How to use GitOps to make changes to a live production cloud." It could have the how-to and sparse-why content (useful for Project Contributors and Open Source Developers) from one location (a repo?), which can be combined with the full what/how/why of a beginner's viewpoint into a single ready-to-teach module.

That's already 48 unique combinations to cover four pathways, and within those modules it might be 3x to 5x more when combining pieces to form a specific module.

Is this a repos problem? A branching problem? A nesting folders problem? Or  something else?

Kind regards,

- Karsten