Maintaining activity web information
|
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
|
- Develop your activity
- Host it on sugarlabs.org
- Create a web page for it here in Category:Activities
- with semantic information from 'Edit with form]'
- if you like, with the attractive
- Create a little fragment called "Activities/My Name (latest)" for it and transclude this in Activities/All
- Should it be invited to be a part of an Activity group, create similar fragments "Activities/8.2/My Name (latest)" and someone else will transclude this in the appropriate page such as Activities/G1G1/8.2, Activities/G1G1, etc.
- Once the latest version no longer works for a particular release or stream, create a separate fragment for that, such as "Activities/8.2/My Name (8.2)"
Contents
Your activity's web page
Alas Creating an activity and its buttons seems out-of-date. Do not use this. Instead, copy what you understand from an existing activity page. TODO: An acceptable template
- It should be in Category:Activities
- It must have semantic information in it.
- Pages in Category:Activities get an '[Edit with form]' tab button, you should click this and fill in information about your activity. This will ensure your activity will show up in pages like
- It should have screenshots
Software update can automatically update
Software update
The Software update Sugar control panel will consult a series of web pages to find the most recent version for the release the laptop is running, and will install or update to that version. This requires that
- the right web pages exist
- the web pages have the information in the right machine-readable format
Your own activity
You can mention a URL to contact in the activity.info file, see Activity_bundles.
Activity groups
Laptops in the G1G1 program (and possibly country deployments) are configured to install a set of activities known as an Activity group.
Do not add your activity to a group, except perhaps Activities/Joyride. The decision as to what activities and collections belong in a group is not yours to make!
Fragments for activities
Here seems to be the way activities in the activity groups are set up. They all use the template {{Activity-oneline}}
| Name | Description | Sample |
|---|---|---|
| Activities/My Activity (latest) | This is the latest version of your activity available. It should match the primary information from '[Edit with form]' on your activity's web page. | Activities/Etoys (latest) |
| Activities/My Activity (8.2) | This is version of your activity that works with release 8.2.0. If that version is identical to the latest, then you can make it a #REDIRECT page to the latest. The moment your latest version no longer works with 8.2 you need to maintain this separately. | Activities/Etoys (8.2) |
You don't need a fragment for earlier releases than 8.2.0 since they did not have the Software update feature. But you can track these in your activity's web page.
A better way
There's way too much update here.
See Semantic MediaWiki for a better approach.
- [Edit with form] should produce the Activity microformat on the activity page
- the [Add another version] button should be separate properties so there's no ambiguity about latest version, latest URL, etc.
- This could be a <noinclude fragment.
- the OBX badges should fill in with semantic info if present
