HowTo write KOffice Documentation
KOffice Documentation Guidelines
There are many things that are common to all KOffice handbooks. A KOffice handbook should:- introduce the user to the workflow of each component
- fully describe the functionality, including examples and short tutorials
- use screenshots wherever appropriate - visually appealing documentation is better than just text
- contain a command reference that explains all menu items (including context menus)
Tips and Tricks
Here are some tips about your editor:
- set your editor to wrap lines at 80 characters
- open and save as utf8 in your editor
- choose the docbook syntax highlighting
- do not indent your docbook files
Screenshots: theme, style and color can be set in KControl. Theme and
style are Plastik and color is KDE default.
Please use those KDE defaults as much as possible for consistent screenshots
along with standard fonts.
Information on KDE Documentation
You can find a lot of information on how to write KDE documentation at
http://i18n.kde.org/docs/
All KDE documentation guidelines found there also apply for
KOffice documentation unless stated otherwise here or in the KOffice
Documentation Cookbook (soon to be available).
Last update: 2008-02-15
The KOffice Project