Get Involved/documentation: Difference between revisions

From KDE Community Wiki
(→‎The KDE DocBook format: remove some obsolete links)
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Get Involved with KDE Documentation ==
== Get Involved with KDE Documentation ==


[[Image:documentation.png|Documentation|left|60px|margin:10px]] 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.
[[Image:documentation.png|Documentation|left|60px|margin:10px]] Writing documentation is a great way to start improving your application and KDE software. Your words will be translated to all languages covered by the KDE translations teams, and you will be helping millions of KDE software 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. The remainder of this page focuses on help documents (application manuals), which include screenshots and explain an application's features and overview.
There are two kinds of documentation in KDE.<br /> Context help explains individual GUI items on the screen. The remainder of this page focuses on help documents (application manuals), which include screenshots and explain an application's features and overview.
Line 7: Line 7:
== Communicating with the team ==
== 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 list [https://mail.kde.org/mailman/listinfo/kde-doc-english kde-doc-english], [http://kde.org/support/#mailinglists learn about mailing lists].
There are many ways to get in touch with the team:<br /> You can chat with the team in the [https://webchat.kde.org/#/room/#kde-docs:kde.org #kde-docs] channel on [[Matrix]] or the freenode [[Internet Relay Chat | IRC]].<br /> The team discusses activities on the mailing list [https://mail.kde.org/mailman/listinfo/kde-doc-english kde-doc-english], [http://kde.org/support/#mailinglists learn about mailing lists].


== Getting the resources ==
== Getting the resources ==


In order to document KDE projects, you will want to run a recent [[Guidelines_and_HOWTOs/Build_from_source | 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! This full manual will be useful: [http://l10n.kde.org/docs/doc-primer/ The documentation Primer]
In order to document KDE projects, you will want to run a recent [[Guidelines_and_HOWTOs/Build_from_source | development version of KDE software]]. 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! This full manual will be useful: [http://l10n.kde.org/docs/doc-primer/ The documentation Primer]


== The KDE DocBook format ==
== The KDE DocBook format ==
Line 17: Line 17:
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:
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://opensource.bureau-cornavin.com/crash-course/ DocBook Crash Course] --- site has moved to www.workshop-chapina.com, but no longer seems to offer the crash course. The same document is found here: -->
* [http://slackermedia.info/sprints/multimediaSprint_v1/ebooks/docbook_crashCourse.pdf DocBook Crash Course]
* [http://l10n.kde.org/doc/screenshots.php The screenshots specification]
* [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://quality.kde.org/develop/howto/howtodocs.php Documentation HOWTO] - more information that should be copied here later-->
Line 28: Line 29:
== Tasks ==
== 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:
Now that 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
* [http://l10n.kde.org/docs/current.php Open Documentation Tasks] - a list of the few documentation priorities

Revision as of 07:19, 31 March 2019

Get Involved with KDE Documentation

margin:10px
margin:10px

Writing documentation is a great way to start improving your application and KDE software. Your words will be translated to all languages covered by the KDE translations teams, and you will be helping millions of KDE software 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.
Context help explains individual GUI items on the screen. 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:
You can chat with the team in the #kde-docs channel on Matrix or the freenode IRC.
The team discusses activities on the mailing list kde-doc-english, learn about mailing lists.

Getting the resources

In order to document KDE projects, you will want to run a recent development version of KDE software. To document third-party projects, you will also need a recent version of that program. There is a special 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! This full manual will be useful: The documentation Primer

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:

Tasks

Now that you have a recent version of KDE running, you can get you first contribution committed today! Here are some tasks for the beginner:

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 (lueck at hube-lueck dot de)
    documentation
  • Yuri Chornoivan (yurchor at ukr dot net)
    documentation
  • volunteer to mentor!
    your name here