Confirmed users
3,193
edits
Michael's Notes: Difference between revisions
→KB Contributor
Michaelverdi (talk | contribs) |
Michaelverdi (talk | contribs) |
||
| Line 105: | Line 105: | ||
=== KB Contributor === | === KB Contributor === | ||
*Improve the knowledge base link takes you to Contributing to the Knowledge Base. | |||
*Contributing to the Knowledge Base has "What to help?" as a section. | |||
*Again my feeling with all of the contributor documentation is that it doesn't lay things out clearly. What should I expect. Where do I start? Then what do I do next? | |||
*It's suggested to go to the contributor forum and read helpful comments threads but I don't understand what to do next. Do I just go around implementing all user suggestions? | |||
*Screenshot and Screencast documentation needs to be updated. Should have some good tutorials for making good sceenshots and screencasts - not just how to insert them in the wiki. | |||
*It would be great if we can get a tool like the [http://www.mirovideoconverter.com/|Miro video converter] specially written for SUMO use (it's just a simple GUI for ffmpeg2theora). | |||
*Flash videos are required but there are no instructions for creating a flash video. | |||
*There is a section on "Making edits" with the first step of: Go to the knowledge base article you want to edit. How would I know what article to edit? How would I know what edits to make? | |||
*What if I don't know how to use IRC? | |||
*I'd like to take a well written article as an example and mark it up with what I was thinking/the reasoning behind everything. I think that would make a better style guide. | *I'd like to take a well written article as an example and mark it up with what I was thinking/the reasoning behind everything. I think that would make a better style guide. | ||