Description
The reason I have not migrated Music Blocks to the sugarlabs project on github is due to the fact that we have not yet set up sugarlabs.github,io.
The basic idea would be to write some scripts to do the following:
(1) Build a landing a page for sugarlabs.github.io
(2) The content of this page should be driven by the README.md files on the various Sugar Labs repositories;
(3) Artwork can be extracted from the activity icons (and screenshots);
(4) This page must be generated via a script so it is "maintainable"
(5) Set up a webhook so that the script can be triggered whenever a repo is changed.
We can also define a heuristic to determine which activities can be run from sugarlabs.github.io, e.g. Music Blocks.
But essentially, it will be an auto-generated help site for Sugar Labs based on repo content. (We have a separate project for migrating the wiki help content into the individual repos. We could also write a script to auto-populate the Sugar Help activity, but again that is a separate project.)
Activity