Activities/Help

Goals of the Help Activity

1. Provide users with easy access to documentation and manuals
2. Let people understand that Sugar is a Community Project and that we would like their help
3. Invite users to join the community by asking a question
4. Make visible the fact that we are real people

User Experience

I am hoping our design people will help here. I think it should be a blurb about being a community project, invitation to as a question and a link to the manual in a reader.

Specific tasks we should be sure to cover

• providing information how to setup network --> just explaning to go to F1 and to click on the essid
• function buttons F1-4 => minimal information about views world,group,me,journal/activities,
• how to set language => short cut to setting menu.

Asking a Question

We don't have a email client so we'll need people to ask a question on a web page. We'll need to explain to them that they can't use it if they are offline.

We should ask for the email address so we can answer them.

For a first iteration questions will be directed to IAEP and community members will be asked to reply. Replying with a link to an FAQ or Wiki page with an answer is to be encouraged.

If we get into any sort of dialog with the question we should invite them to subscribe to IAEP and to help the community.

Nice to Have Features

• Look up what version of Sugar they are running and point them to the appropriate manual for that version.

Next Steps

• Put the content of the help activity into a form that can be managed with version control so we can make different versions for the XO and SoaS and potentially let deployments customize it. - Ticket 885