Feature: Branch views #390
Description
Which module(s) and week(s) does this change affect?
Module(s): all
Week(s): all
What is the work that needs to be done?
I'm considering this only
If we were to create a close fork for MigraCode, what might we want to do? I think we want their content to be available to CYF as well, right? So a common pool of blocks? Should we move blocks to an independent repo: curriculum blocks and refactor this as a platform only repo? Will github actually just block us if we create everything via their api...
Should we create a Hugo theme that swaps out all the CodeYourFuture org links to MigraCodes but expects their modules to be forks of ours?
Should we have a spanish language switcher? That seems pretty old school. I feel like a fork switcher might be better.
Should we create an independent workshops section anyway, and just pull in all workshops and tag em so mentors can get a view more easily?
Why is this work important to do?
If we can understand how to merge with MigraCode, we will be closer to creating a truly useful curriculum & platform.
Additional context
Who might need to know about this change?