Difference between revisions of "Activities/Help"
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
a web page. We'll need to explain to them that they can't use it if | a web page. We'll need to explain to them that they can't use it if | ||
they are offline. | they are offline. | ||
| + | |||
| + | ==Nice to Have Features== | ||
We should ask for the email address so we can answer them. | We should ask for the email address so we can answer them. | ||
Revision as of 14:09, 25 May 2009
Goals of the Help Activity
- Provide users with easy access to documentation and manuals
- Let people understand that Sugar is a Community Project and that we would like their help
- Invite users to join the community by asking a question
- 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.
Nice to Have Features
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.