Open walterbender opened 6 years ago
The reason I have not migrated Music Blocks to the sugarlabs project on github ...
Not having Music Blocks repository in the sugarlabs organisation need not block on this, so I've forked it for the time being. We can delete it later if not needed.
Is this issue resolved?Seems to be !If not I can take up this if you want!
It is not resolved. It would be great to be able to access all of the web-enabled activities this way (including Music Blocks).
See https://srevinsaju.github.io/sugar-docs/ for a similar implementation of the docs repo Fork of sugar-docs
Is this issue resolve if not can I help to resolve this issue, just tell how can should it start should i used react.js or simple html-js files for doing this
Is this issue resolve if not can I help to resolve this issue, just tell how can should it start should i used react.js or simple html-js files for doing this
Hey @AniruddhaGawali, I don't know if you went through the earlier comments but you should if you didn't as it does answer your question and about what to use, I think it'll be easier to use what you consider would be best for the issue and open a PR clearly stating why you used that method then a discussion can be started.
For how to start, you might want to take a look at creating a github page as that's the aim of this issue, you can try creating one yourself so you understand how it works, the opening comment has more info. Hope that helps!
@chimosky i guess this issue has be solved
@chimosky i guess this issue has be solved
No it hasn't been solved.
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.)