Wiki Editing Policy

From Apache OpenOffice Wiki
Jump to: navigation, search

Template:Documentation/Banner Template:Documentation/DraftPage

This article helps you to contribute effectively to the Documentation part of the wiki. We strongly encourage you to announce new pages or major changes to the mailing list

Project-independent ruleset


Prerequisites for Editing

You must be registered and logged in before you can edit the Wiki. Registration is easily done.

  1. Click on Log in / create account in the upper right corner of the screen and enter the required bits.
  2. Subsequently you have to validate your email address.

For further logins you use the same entry point, enter Username and Password, and click the Log in button.

Documentation caution.png To combat vandalism, newly registered users cannot edit any page or create a new page until a four (4) day "cooling off period" has elapsed.

The next step could be to tell the Community about yourself. There is definitely no harm and it is a good way of getting comfortable with the Wiki.

  1. When you are logged in, your username shows at the top of the page, in red, until you create your user page. Click on your username to do that.
  2. On your page, add some sections as given below, as it is your profile on the OpenOffice Wiki;
    • About yourself
    • OpenOffice and you
    • Your contributions
    • Work in progress
    • Any future plans?
    • Reference (optional)
    • Contact

So, this is somewhat of a template, for creating a profile. You may or may not need to follow this template, you may have sections of your choice. This is done to make a uniform profile for all the new users.

Adding Comments

Important comments should be announced on the mailing list to be sure that they get noticed.

To add a comment to a page

  1. Click the Discussion tab on the top of the page.
    • If you are starting a new topic click on the + sign to the right of the edit tab at the top, fill in the subject line and write your comment in the main text box.
    • If you want to add a comment to an existing discussion leave it after the existing comments and indent it by putting one or more colons (:) at the beginning of each paragraph.
  2. Sign your username with four tildes (~~~~). You can do this automatically with the signature with timestamp button ( button_sig.png ) on the toolbar.
  3. Click Save Page.

To learn more about comments see the Mediawiki help about talk pages

Structure of the Documentation Section of the Wiki

The Documentation section is only part of the large Wiki. The doc.oo.o project tries to present the information in this section in a way that it is easily accessible and has a structure that allows straightforward navigation for both users and contributors.

All documentation pages are subpages of the main Documentation page. A further substructure presents sections as subpages containing further subpages. Think of it as a hierarchical representation, just like a file system. Every subpage is automatically linked back to the main page.

The current wiki page tree looks like this:
   +---Administration Guide
   +---How Tos
   +---OOoAuthors User Manual
   +---OOo3 User Guides
   +---Samples, Templates and Clipart
   +---Setup Guide
   +---BASIC Guide
   +---Building Guide
Subpage Description
Documentation/Dashboard High-level tracking of documentation sub-projects and content deliverables
Documentation/Administration Guide Guide that describes how to administer an network installation
Documentation/FAQ Collection of FAQs.
Documentation/How Tos Link collection of How Tos
Documentation/OOoAuthors User Manual Collection of 2.x User Guides from OOoAuthors
Documentation/OOo3 User Guides Collection of 3 User Guides from OOoAuthors
Documentation/Tutorials Tutorial collections from different contributors
Documentation/Samples, Templates and Clipart Sub-project page in order to provide usable templates for business and personal use (draft)
Documentation/Setup Guide Sub-project page in order to provide a guide through the setup process of (in progress)
Documentation/BASIC Guide Guide that provides an introduction to programming with BASIC
Documentation/Building Guide Guide that describes how to build the Apache OpenOffice software yourself, from source.
Documentation/DevGuide Guide that describes how to program with using the component technology UNO (Universal Network Objects) with
Documentation/Reference Collection of reference material. References on this page should show up under Reference Lists at the Documentation main page.

Creating new Pages

Documentation caution.png Before creating a page make sure that there is not already an existing page with a similar topic.
  • If the new page can be a subpage of an existing page simply go to the existing page and create a link to the new page. After saving the page with the link you can click the link and start writing on your new page.
  • If you want to create a really new page for the Documentation project, you can use the wiki's URL for creating a new page. You should observe the wiki page tree when you create a new page in this way. The URL to a wiki page is then something like this: Name
  • However, the recommended method is to search for the desired page name (in the Search field above left), and when the page does not exist, you will be offered to "create this page" by clicking on a link on the Search Results Page.


For more information about new pages see the Mediawiki help about new pages

Using Categories

The Categories that are assigned to a page are usually listed at the bottom of the page. Click on a Category, and you will view a topic page with all the pages that have been classified in that Category. This way, a Category tag in a page gives you the opportunity to look up related contents. The bigger the page the more Category tags might be inserted

To add a Category tag to a page

  1. Click Special pages in the toolbox on the left side.
  2. Click Categories in the Special pages link list.
  3. Choose a Category name that makes sense, and apply it by adding [[Category:''Category Name'']] at the end of the page.
Documentation caution.png Do not create duplicate Categories for the same topic. Each Category must be unique. Otherwise it will be difficult to use the Categories for searching the wiki.

Look at MediaWiki Help:Categories if you want to know more about Wiki Categories.

A simple example of how to use Categories in Wiki books:

  1. Create a Category named after the current chapter.
  2. Add the new Category tag to all pages of that chapter
  3. Add the Category tag for the book to the newly created Category page.

The reader can then view the book Category. The book Category shows all the chapters in the book. If the reader clicks on a chapter Category, they can see all of the pages in that chapter (in alphabetical order).

Do not add a category and its subcategory to the same wiki page. For more information see the MediaWiki Help:Category section on Category considerations.

You can use Templates to add a common category to a large group of pages, but it is not recommended. It may appear to save time, but "adding or deleting a category tag in the template does not add or delete the listings on the category page of pages that use the template, until some edit is made in the page that uses the template." For more information, see the MediaWiki Help:Category section on Using templates to populate categories.


Look at the Templates help if you are unfamiliar with mediawiki templates.

Adding a new Documentation Template

  • If you create a new template to be used in the wiki documentation, name it as a subpage of Documentation.
    • wrong: mytemplate
    • right: Documentation/mytemplate
  • Add a description of the template purpose and usage to the template itself using the element as described in MediaWiki help: Template.
  • Add the template to the list of templates below.

List of Existing Documentation Templates

This is a list of Documentation templates and their usage 
Template Name Usage Example
Template:Documentation/Banner Puts the Documentation Project "Banner" at the top right of the page


Template:Documentation/OOo Displays an logo


Template:Documentation/PDF {{Documentation/PDF}} Template:Documentation/PDF
Template:Documentation/PRODUCTNAME A variable for displaying the string


Template:Documentation/AOO A variable for displyaing the string Apache OpenOffice


Template:Documentation/hbar Used to draw horizontal bars for simplistic bar charts


Template:Documentation/hbar Template:Documentation/hbar Template:Documentation/hbar

Template:Documentation/BeingEdited Marks a page as currently being edited to avoid conflicting changes.

Use this template when you perform larger edits on a file that may even take more than one session to finish. Be sure to add name and date of "locking" by adding a ~~~~ as parameter: {{Documentation/BeingEdited|~~~~}}

Template:Documentation/NeedsRework {{Documentation/NeedsRework}} Template:Documentation/NeedsRework
Template:Documentation/HelpNeeded {{Documentation/HelpNeeded|Check the spelling}} Template:Documentation/HelpNeeded
Template:Documentation/CheckedAccuracy Marks up pages that have been reviewed for accuracy.

Be sure to add name and date of review by adding a ~~~~ as parameter: {{Documentation/CheckedAccuracy|~~~~}}

Template:Documentation/Outdated Identifies a page that is obsolete


Template:Documentation/DraftPage Marks up pages that are in a draft state


Template:CoreCriticalTemplate This template is intended to mark the Core Critical Template, unconsidered intervention in the template may result in the destruction of the entire project!


CoreCriticalTemplate.png  Критически важный опорный шаблон    —    Core Critical Template.  

Необдуманное вмешательство в шаблон может повлечь за собой разрушение всего проекта! Unconsidered intervention in the template may result in the destruction of the entire project!


Template:Documentation/Imported {{Documentation/Imported|author=Author Name|contributors=Contributor Names}} Template:Documentation/Imported
Template:Documentation/Windows Displays a Windows logo and allows to enter Windows specific content.

{{Documentation/Windows|Windows related content}}

Template:Documentation/Linux Displays a Linux logo and allows to enter Linux specific content.

{{Documentation/Linux|Linux related content}}

Template:Documentation/OSX Displays an Apple/OSX logo and allows to enter OSX specific content

{{Documentation/OSX | Mac related content}}

Template:Bug Links to Issuezilla issue.


Issue 123456
Template:Documentation/Note Takes sections containing notes,i.e. related, reinforcing information, for example, an explanation or comment.

{{Documentation/Note|Notable stuff}}

Template:Documentation/Tip Takes sections containing tips, i.e. useful non-crucial information, for example, a keyboard shortcut.

{{Documentation/Tip|Right-click opens the context menu}}

Template:Documentation/Caution Takes sections containing warnings, i.e. information that is potentially harmful in some way, for example, data loss.

{{Documentation/Caution|Always switch off power before opening the case.}}

Documentation caution.png Always switch off power before opening the case.
Template:Documentation/SeeAlso and Template:Documentation/DevGuide/SeeAlso {{Documentation/SeeAlso| * [[Documentation/OOo3_User_Guides/Getting_Started|Getting Started with 3.x]] }}
  • DevGuide/SeeAlso version is used in the Developer's Guide and is set to be excluded from generated PDF and ODT books.
Template:HeaderBlock Ornamental template.

Designed to process the most important links in the form of the similarity of a button. {{HeaderBlock|[[Documentation]]}}

Template:Documentation/FromForum {{Documentation/FromForum}} Template:Documentation/FromForum
Template:Documentation/Abstract Takes a short abstract of the chapter content of guides. Add to the top of guides.

{{Documentation/Abstract|Abstract Text}}

See, for example, this Administration Guide Chapter
Template:Documentation/*TOC Several tables of content based on Template:Documentation/MasterTOC used in guides. See, for example, the Basic Guide TOC
Template:Documentation/MasterTOC This is the master template that is used to create tables of content. For usage click the template name.
Template:Documentation/OOoVersion This template is used to insert an version box on a page.


Template:OOoW This template is used to insert an Apache OpenOffice Writer string in text.


Apache OpenOffice Writer
Template:OOoC This template is used to insert an Apache OpenOffice Calc string in text.


Apache OpenOffice Calc
Template:OOoCh This template is used to insert an Apache OpenOffice Chart string in text.


Apache OpenOffice Chart
Template:OOoI This template is used to insert an Apache OpenOffice Impress string in text.


Apache OpenOffice Impress
Template:OOoD This template is used to insert an Apache OpenOffice Draw string in text.


Apache OpenOffice Draw
Template:OOoB This template is used to insert an Apache OpenOffice Base string in text.


Apache OpenOffice Base
Template:OOoM This template is used to insert an Apache OpenOffice Math string in text.


Apache OpenOffice Math
Template:POOo This template is used to insert an Portable

string in text. {{POOo}}

Template:SRB This template is used to insert an 'Sun Report Builder' string in text.


Sun Report Builder
Sun Report Builder
Template:MSO This template is used to insert an Microsoft Office string in text.


Microsoft Office
Template:MSO2003 This template is used to insert an Microsoft Office 2003 string in text.


Microsoft Office 2003
MSO 2003
Template:MSO2010 This template is used to insert an Microsoft Office 2010 string in text.


Microsoft Office 2010
MSO 2010
Template:MSW This template is used to insert an MS Word string in text.


MS Word
Template:MSE This template is used to insert an MS Excel string in text.


MS Excel
Template:MSA This template is used to insert an MS Access string in text.


MS Access
Template:MSPP This template is used to insert an MS Power Point string in text.


MS Power Point
Power Point
Template:MSEq This template is used to insert an MS Equation string in text.


MS Equation
Template:MSV This template is used to insert an MS Visio string in text.


MS Visio
Template:Key This template is used to insert keycodes in text.


 Ctrl  +  ⇧ Shift  +  → 
Template:Button This template is used to insert an article in the notation of buttons on-screen dialogues.


Template:QuoteEn The template is designed for inserting quotations in the text.


Quote 3 is the leading open-source office software suite for word processing, spreadsheets, presentations, graphics, databases and more.

why.openoffice.orgQuote bg2.png

Template:Menu This template is designed to insert text anywhere in the chain menu.

{{Menu|File|Open|Print|и т. д.}}

File → Open → Print → 4 → 5 → 6 → 7 → 8 → 9 → 10
Template:Path This template using to format file system path.

{{Path|C:\Program files\}}

C:\Program files\

Graphical Content

General guidelines for images are:

  • Use a descriptive and unique title. The filename should be constructed in a way so it shows the usage, e.g. Doc_mig_icon_data.png = Documentation image, used in the migration guide, depicting the database icon.
  • If possible, do not pre-scale the images you are uploading. You can use the MediaWiki image thumbnail feature to scale the image.
  • Edit the image if necessary to make sure that the important part is clear and visible.
  • Keep in mind that people may be translating the page where you are placing an image. Try not to include callouts or other extra text on the image.
  • JPG is usually best for photos, SVG, for icons, logos etc, and PNG for screen captures. Try not to use BMP.

Before you can insert your well prepared image in a wiki page you have to upload it.

  1. In the sidebar, under toolbox, click Upload file. The image description page will appear.
  2. Use the image description page to describe an image and copyright status (if any).

To place the image on a page you can use the MediaWiki Image thumbnail feature which "wraps" your illustrations in an image box. This image box includes a spot for an image caption. The syntax is
Image caption
, where:
  • thumb = thumbnail the image and wrap in an image box
  • position = position on page. "none" places the image on the left of the frame with no text wrapping. "left" and "right" places the image on the left or right of the page with full text wrapping.
  • size = max width in pixels for the image. If the image is larger than this value it is scaled down. If the image is smaller it is left as is.

If you do not declare a position and size, the image is scaled to a small thumbnail, and defaults to the right hand side of the page with full text wrapping.

Here is an example using [[Image:LoadSaveOptions.png|thumb|none|500px|An example image caption]]

An example image caption
  • How to handle image and table numbering?


Although the editing window offers assistence in writing internal and external links look at the MediaWiki help page about links for a better understanding of how links are working in wikis.

There is another MediaWiki help page if you need some examples.

When creating link text consider the guidelines for using links in our style guide.

General Editing Work

Editing is only possible after login. You can start editing the whole page after clicking the edit tab at the top. But usually it is more comfortable to edit individual sections of a page by clicking one of the [edit] links on the right side. If you make changes, please consider the rules of the style guide to assure a consistent writing style. Click the Show preview button before you save the page finally.

Fixing inappropriate, inaccurate, or outdated content

Contents that are not up to date are usually marked by one of the following labels:

This label means that an article is outdated as a whole and needs to be revised completely.
Template:Documentation/HelpNeeded If an article is partly outdated or inaccurate you may find this label asking for specific help.
Template:Documentation/NeedsRework You can find a collection of pages with this label if you click on Pages that Need Help! on the Wiki main page.

When you have selected a page to work on

  1. test whether the described procedures are still valid for the current version of
  2. log in and make the necessary corrections.

This works best when you open two tabs in the browser, one for reading the procedures and another for editing.

When you have finished, remove the above label(s), mark the page with the label "Checked for technical accuracy" (as described in the Templates section above), and click Save page.

Fixing minor errors and typos

If you detect minor errors like typos, just log in and edit the article. Before clicking on the Save page button you might check the This is a minor edit box above.

Fixing graphics and screenshots

To edit a graphic in the wiki, right-click the graphic and choose Save image as. When you have edited the graphic on your computer, go back to the wiki page, click the graphic, and in the image description page choose Upload a new version of this file.

If you have created a new version of a screenshot, directly click the corresponding screenshot in the wiki and then Upload a new version of this file in the image description page.

Fixing Style and Language

Articles that need improvement in style and language might be recognized by the following labels: Template:Documentation/HelpNeeded Template:Documentation/NeedsRework You can find a collection of articles with the latter label if you click on Pages that Need Help! on the Wiki main page.

To improve such an article, just log in, click on the edit tab and make the necessary corrections. Then remove the label(s) and click on Save page.

Linking to localized pages

  • Link the various languages to each other using the Interwiki links syntax [[ISO_Lang_code:Page_Title]].
    For example, [[zh:Zh/Documentation/DevGuide/OpenOffice.org_Developers_Guide]] adds a link to the Chinese translation of the first page of the Developer's Guide. This link shows in the left column, under the heading "In other languages". This may be more practical to do with Wiki Templates as more languages are added.
  • In the Developer's guide we use a template to link translated pages.
    The Wiki Syntax is: {{Documentation/DevGuideLanguages|Page_Title}} where Page_Title is the current Wiki page name.
    For example, {{Documentation/DevGuideLanguages|Documentation/DevGuide/ Developers Guide}} will add the localized page links for the first page in the Developer's Guide.
    If you want to see a link to your language at the Developer's Guide wiki pages simply add your language to the template Template:Documentation/DevGuideLanguages. For example, for Dutch you would have to add [[nl:NL/{{{1}}}]]. Make sure the template is referenced correctly in each of the translated pages.

Validating Content

Fixing Spam / Deleting Pages

If you detect spam you can send an email to the dev@ list.

There is also a list of Wiki Sysops (people who can delete pages). If you want to have pages deleted, you can either ask someone from that list, or better, add the Wiki Syntax {{delete}} anywhere on the page you want to be deleted. This will add the page to the "Candidates for speedy deletion" category, and the page will be deleted by someone with Sysop privileges, or by WikiBot maintenance.

Working on FAQs

Every question together with its answer is displayed on one single wiki page.

If you want to insert a new FAQ entry, that is, a pair of a question together with the corresponding answer:

  1. Select a FAQ section on the main page of the Documentation Wiki. In Writer and Calc you have to select another subpage until you reach a final FAQ section.
  2. Scroll down to the Insert New FAQ listbox.
  3. Replace the text in the listbox after the last slash '/' with your question.
  4. Click Add New FAQ
    A new wiki page will be created and preloaded with a template for a Q/A pair:
    <section begin=question/>
    <section end=question/>
    <section begin=answer/>
    <section end=answer/>
    [[Category:Documentation/FAQ/<INSERT FAQ SECTION>]]
  5. Replace (INSERT FAQ TITLE) with the title of the FAQ to be displayed on the page. This may be a short version of the question or the question itself.
  6. Replace <INSERT QUESTION> with the actual question.
  7. Replace <INSERT ANSWER> with the actual answer.
  8. Replace <INSERT FAQ SECTION> with the current FAQ section name. This category assignment determines where this wiki page will appear. Please use the following section names:
  9. FAQ section section name in category
    General General
    Installation Installation
    Word Processing Writer
    Automatic Functions Writer/AutomaticFunctions
    Document Management Writer/DocumentManagement
    Formatting Pages and Docs Writer/FormattingPagesAndDocuments
    Formatting Text Writer/FormattingText
    Graphics, Frames & Objects Writer/GraphicsFramesObjects
    Indexes, Tables of Contents Writer/IndexToc
    Printing and Mail Merge Writer/Printing
    Spreadsheets Calc
    Drawings Draw
    Presentations Impress
    Formula Editor Formula
    Database Databases
    Macros Macros
  10. Click Save Page.

Working on How Tos

If you want to create a new How To

  1. Go to the How Tos section and open the edit window.
  2. Identify the adequate subsection and enter the title of your How To as a link.
  3. Click Save Page to make the link visible.
  4. Click the link to your How To and start writing by using the rules of the style guide. If you are not sure about how to implement the style guide, have a look at the Writer How To Getting a Picture Into the Gallery.


You can also create How Tos by writing a new page like Documentation/How Tos/Page Name with one or more specific categories. The newly created How To page will then be assigned to the corresponding How To sections. The available categories for that are the following:

  • [[Category:Documentation/How Tos/Installation]]
  • [[Category:Documentation/How Tos/Writer]]
  • [[Category:Documentation/How Tos/Impress]]
  • [[Category:Documentation/How Tos/Calc]]
  • [[Category:Documentation/How Tos/Database]]

If you want to revise existing How Tos, watch for the label "This article needs to be checked for accuracy and style."

  • Test whether the described procedures are still valid for the current version of,
  • check whether the rules of the style guide are applied,
  • check for grammar and spelling mistakes,

and make the necessary corrections in the edit window.

When you have finished, mark the page with the label "Checked for technical accuracy" as described in the Templates section above, and click Save page.

Do not forget to notify about your work on the How Tos.

Working on Guides

Currently, there are the following guides on the wiki:

If you want to work on the User Guides for please contact the OOoAuthors group.

There is some help available about Contributing to the Developer's Guide which may also be useful for the Administration Guide and the BASIC Programming Guide.

Localizing Content

Here are some general guidelines for translations:

  • If possible, follow the same structure as the original page.
  • If possible, do not translate the Wiki page names. Use the {{DISPLAYTITLE:Page title}} to localize the page name. Using the same page name makes it easier to identify translated pages and easier to automatically link from one page to another
  • Use a subpage naming structure that clearly indicates the language of the page. For example, the Swedish version of a page could use SV/Pagename/. See Help:Page naming
Documentation note.png If possible, try to always use all-caps for the ISO language code.
  • Communicate with the L10N and NLC communities and let them know what you're doing.
  • If in doubt, ask. The Documentation, and NLC communities are here to help you.

The L10N community is working on a process and toolset for translating Wiki pages.

Translation steps

There are (currently) no tools or mechanisms in place in the Wiki to assist with translations. The basic translation process is:

  1. Identify a page that is to be translated.
  2. Click Edit on that page.
  3. Select all Wiki text in that page and copy it.
  4. Cancel the edit.
  5. Start a new page with the right page name for the new translated article (see Help:Page naming).
  6. Paste in the copied original language text.
  7. Click Save Page to give yourself a start point.
  8. Translate the text on the newly created page.

Content on this page is licensed under the Public Documentation License (PDL).
Personal tools
In other languages