Sugar on a Stick/Activity Criteria: Difference between revisions
| Line 37: | Line 37: | ||
=== Have a usage frontpage === | === Have a usage frontpage === | ||
'''Rationale:''' Users should | |||
'''Test:''' The ASLO page for an Activity should include a link called "instructions for users" (note: this is fairly arbitrary and we may want to standardize on a better title/format) that leads to a tutorial on how to start and run the Activity in question. This can be anything from a page on the Sugar Labs wiki with screenshots all the way up to a [http://en.flossmanuals.net/ flossmanuals book] on just that Activity. | |||
Suggested things for inclusion: | |||
* what the Activity does | |||
* intended audience (what assumptions does the design make? does it assume you can read, add, etc?) | |||
* how to install it (can link to generic Activity instructions) | |||
* how to start it (can link to generic Activity instructions) | |||
* how to uninstall it (can link to generic Activity instructions) | |||
* how to stop it (can link to generic Activity instructions) | |||
* an explanation of the interface (what do the different buttons, etc. do?) | |||
* how to begin exploring it (this can take several forms: a walkthrough of a few basic tasks, some hints on exercises/things-to-try, a link to galleries of existing work and classroom stories of that Activity's usage, etc.) | |||
'''Instructions:''' We need to write instructions and gather more examples for this. Right now the best examples are the [http://en.flossmanuals.net/ flossmanuals books] on various Activities, but to expect every Activity to do a book seems like too much - we need examples of a good minimum bar, which is likely to be a well-made wiki page. | |||
=== Have a development frontpage === | === Have a development frontpage === | ||