Hi Jonathan, :) It's truly encouraging to hear your willingness to help out, and the documentation team will readily accept any contributions that you would be willing to offer. Really nice to see people putting efforts in to give back to the community =). A bit of preamble:
KDE uses Docbook for its documentation, but you by no means have to know it (and indeed, it is recommended that you don't use it at all at first); what is in dire need in the world of documentation is the content. A lot is missing and/or needed. :) It is entirely up to you how much time you put in, and even a few hours a week is really great news. The doc websites are currently going through an update and hence in a state of transition, but here are a few useful links: http://docs.kde.org/ -- you should be able to easily access any KDE handbooks/docs from there, including any ones in extragear. http://i18n.kde.org/doc/ -- current home. Ok, now to possible/available places for you to contribute. :) If you check here ( http://tinyurl.com/ch3qo ) you will get a list of the bugs, for the documentation team, that are considered ideal or particularly suited for new contributors; ones to easily get you right at it. You should feel free to choose any of those; could be a good idea to go for any of the ones in the userguide there, or you might choose to do one for any of the applications as described there. Take a look through the doc you're planning to work on, and/or at the application that you plan on writing about, and then you can just send the mailing list a text file, with the changes proposed. If you have any questions at all, you shouldn't hesitate in the slightest (really) to fire away and ask them here (or, you can catch us in IRC; join us in #kde-docs under Freenode). I'm pretty new to documentation myself, but, as you will find, there are several very knowledgable (and extremely helpful) persons on the doc team. Once again, welcome aboard, :) Kind thoughts, Francis Giannaros.
