← Get Involved/documentation You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. __NOTOC__ == Get Involved with KDE Documentation == [[Image:documentation.png|Documentation|left]] Writing documentation is a great way to start improving your application and the KDE project. Your words will be translated to all languages covered by the KDE translations teams, and you will be helping millions of KDE SC users to better understand their desktop and applications. Anyone with reasonable English skills and good knowledge of an application can help. There are two kinds of documentation in KDE.<br /> Context help explains individual GUI items on the screen, see [http://bddf.ca/~aseigo/whatsthis_tutorial/ Aaron Seigo's guide] on this. The remainder of this page focuses on help documents (application manuals), which include screenshots and explain an application's features and overview. == Communicating with the team == There are many ways to get in touch with the team:<br /> You can chat with the team in [irc://irc.kde.org/kde-docs <nowiki>#kde-docs</nowiki>] on irc.freenode.net, or [http://kde.org/support/#irc learn more about IRC].<br /> The team discusses activities on the mailing lists [https://mail.kde.org/mailman/listinfo/kde-docbook kde-docbook] and [https://mail.kde.org/mailman/listinfo/kde-doc-english kde-doc-english], [http://kde.org/support/#mailinglists learn about mailing lists]. == Getting the resources == In order to document KDE projects, you will want to run a recent [http://techbase.kde.org/Getting_Started/Build development version of KDE]. To document third-party projects, you will also need a recent version of that program. There is a special [http://l10n.kde.org/docs/tools.php KDE DocBook XML toolchain] used to create documentation. But feel free to write docs in any format you want, and the team will convert it for you! == The KDE DocBook format == We use the DocBook XML standardized format, which allows for ease of translation using our custom tools. The markup is extremely self-descriptive, and many people find it easier than HTML to learn. However, if you are not familiar with it, please read up about it below. To produce quality documentation, please have a look at these guides: * [http://opensource.bureau-cornavin.com/crash-course/ DocBook Crash Course] * [http://l10n.kde.org/docs/styleguide/index.html The KDE Style Guide] - a complete guide to KDE documentation * [http://l10n.kde.org/docs/markup/index.html The KDE DocBook Authors guide] - covers the minimal customizations KDE makes to the DocBook DTD, and the conventions we use within our documentation * [http://l10n.kde.org/doc/screenshots.php The screenshots specification] <!--* [http://quality.kde.org/develop/howto/howtodocs.php Documentation HOWTO] - more information that should be copied here later--> * [http://l10n.kde.org/docs/gettingstarted.php Getting started guide] on the internationalization site * [http://l10n.kde.org/docs/doc-primer/ The documentation Primer] * [http://l10n.kde.org/docs/questionnaire.php Questions You Should Answer When You Document KDE] * [http://l10n.kde.org/docs/index-script.php The goals of the KDE Editorial Team] * [http://opensource.bureau-cornavin.com/crash-course/ Crash-course to DocBook] * [http://l10n.kde.org/docs/tools.php The KDE DocBook XML toolchain] == Tasks == Now you have a recent version of KDE running, you can get you first contribution committed today! Here are some tasks for the beginner: * [http://l10n.kde.org/docs/current.php Open Documentation Tasks] - a list of the few documentation priorities * [https://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=docs&component=Screenshots&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Bugzilla listing of screenshots] that need to be fixed * [https://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=docs&component=Corrections&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Bugzilla listing of documentation] that needs to be updated * [https://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=docs&component=Missing+content&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Bugzilla listing of applications] missing documentation * [http://techbase.kde.org/Projects/Documentation/KDE4 Techbase Documentation page] * [http://techbase.kde.org/Projects/Documentation/KDE4_(health_table) Documentation Status] * Mail in your creations to [mailto:email@example.com the KDE documentation team]. == Mentor program == Getting started in a big project can be hard. Here are some people that are willing to help you one-on-one: * Burkhard LÃ¼ck (<span class="mailme">lueck at hube-lueck dot de</span>)<br /> documentation * Yuri Chornoivan (<span class="mailme">yurchor at ukr dot net</span>)<br /> documentation * volunteer to mentor!<br /> your name here Return to Get Involved/documentation. Retrieved from "https://community.kde.org/Get_Involved/documentation"