Optimize content in Q.wiki for translation

When teams work in multiple languages in Q.wiki, automatic translation helps make knowledge quickly accessible. However, how well translations work in everyday practice also depends on how content is named, structured, and presented.

Even small adjustments can significantly improve translation quality.

Recommendations for translation-friendly content

• Use action-oriented page titles instead of single words.
  Titles with several words provide more context than individual terms. For example, use “Conducting an Online Presentation” instead of simply “Presentation.”
• Whenever possible, link or format entire terms, sentence parts, or bullet points.
  If only individual words within a sentence are linked or highlighted, the context may be lost during translation.
• Name files and attachments as naturally as possible.
  Avoid underscores and file extensions in the title. For example, use “Supplier Evaluation Report” instead of “Supplier_Report.pdf.”
• Use terminology consistently throughout.
  Consistent terminology improves both clarity and translation quality.
• Label language versions consistently.
  Instead of DE, EN, or FR, use clear abbreviations such as [GER], [ENG], or [FR].
• Do not place important information only in images.
  Embedded images, such as process maps, are currently not translated automatically.
  If needed, use separate language versions or bilingual labels.
• Do not rely solely on attachments for important content.
  Attachments and file pages are currently not translated automatically. Content should therefore be placed directly on the Q.wiki page whenever possible.
• Structure content clearly and logically.
  Short sections, clear headings, and lists make content easier to understand and easier to translate.

Additional note

You can find further tips on content design in Q.wiki in the article Tipps for creating content in Q.wiki - Process description vs. Work instruction