🎇 Is XWiki the right fit for your team's knowledge needs? Join our webinar to find out! Register now.

How to choose the best Office application for XWiki

03 Nov 2020 5 min read

Written by

Oana Elena Florea

, Customer Support Manager

Choosing the best Office application for XWiki is not an easy task thanks to the multiple available options, however, we would need to start by analyzing the differences between the OnlyOffice Connector, the Office Importer Application, and the macros GoogleApps and Office365. All applications are used to manage Office content and they are working with very different technologies in addition to each one having its own strengths for different use cases.

The Office Importer Application allows users to convert different Office content to wiki pages using a dedicated server like Libre Office. Next, the newly converted pages can further be WYSIWYG edited, extended inside the wiki with metadata or XWiki objects, exported again as ODT or RTF, etc. The gif below shows how to configure an Office server for a local wiki, by editing a few properties in the xwiki.properties file, starting the wiki, checking the Office server state in the wiki Administration, then how it would look when wanting to create a new page where you would import an Office document.

Import-Office-files-in-XWiki-3-steps.gif

The OnlyOffice Connector allows you to create and edit Office content using a dedicated OnlyOffice server. Such documents will be stored as attachments on wiki pages and edited inside the OnlyOffice editor.

spreadsheets.png

When is the Office Importer Application a better fit?

  • The application is included by default with XWiki, only the Office server would need to be set up (internally or externally managed) for the import of Office content. For optimal results, we recommend our users to set up a Libre Office server.
  • The application is a good fit when the imported wiki content will evolve over time thanks to the contributions from other wiki users. For example, the pages can, later on, be extended with other structured content, metadata (author, creator, page history), and macros (e.g. diagrams, workflow).
  • When in need of a quick export of the latest page content (e.g. to share with external users, send by email, etc), the same Office server will convert the wiki page back to an ODF or RTF document for further use.

The best use cases for the OnlyOffice Connector Application

  • One of the big advantages of this application is the possibility to have several users editing the same document in real-time.
  • Large Excel documents can also be easily updated with a UI similar to the Microsoft Office package.

Other Office Applications to have in mind

  • Office365 Integration would be a good addition to the wiki when users would like to display and to search for Office documents from OneDrive inside XWiki.
  • With the GoogleApps Integration, the user can easily import a Google Apps document as an attachment in XWiki (in multiple formats) or launch editing of an XWiki attachment in Google Apps. Once the editing session is finished the user can reimport it in XWiki.

You can also take a look at the important summary of this article.

You may also be interested in:

Best practices

Knowledge base software vs. content management system: What to choose?

Still deciding between knowledge base software and a CMS? Our latest article breaks down the key differences, must-have features, and real-world use cases to help you choose the right tool for your needs. Plus, we answer the big question: Can you use one in place of the other? Dive in and find out!

Best practices

How to create and customize a XWiki PDF template | Tutorial

Whether you’re managing technical documentation, internal wikis, or public knowledge bases, customizing your XWiki PDF templates lets you create professional, branded documents ready for sharing, archiving, or printing. In this step-by-step tutorial, you’ll learn how to create and customize a PDF template in XWiki — from setting up the template structure using Velocity and XHTML to styling it with CSS and adding dynamic information.

Best practices

Knowledge management vs. content management | Key differences and tools

Though they share some similarities, knowledge management and content management serve different purposes and users, and rely on different tools. Learn from our straightforward comparison about their differences, benefits, and practical applications.