Share:
ClickHelp Documentation

Import from Microsoft Word

In ClickHelp, you can import user manuals stored in the Microsoft Word format to your documentation portal.

As far as Microsoft Word related formats are concerned, ClickHelp supports the following formats for import:

  • DOCX OpenXML, Microsoft Word 2007 and later
  • DOC Microsoft Word 97-2003
  • RTF - Rich Text Format

To import a Microsoft Word document from your PC:

Warning Note that for a Microsoft Word file to be imported to ClickHelp correctly, you need to accept all the changes in this document. For this, when the file in question is opened in Microsoft Word, find the Review tab there and go to Review > Accept > Accept all changes in document. Save the file and proceed with the steps described below.
  • Open your Portal Dashboard and hover the mouse pointer over the plus button. 
  • Click Import Existing Manual
      
  • In the Import Project Wizard, pick Microsoft Word file and where to import the content. You can create a new project or add the topics to an exiting project

  • If you want to create a new project, give it a name and a Project ID.

  • Click Next. You'll see the Import Settings step of the Wizard. First, let's place the Microsoft Word file in the specified area on the left (either drag&drop it or browse the way to the file on your PC), and it will immediately appear in the Uploaded Files.

  • On the right side of the Import Project Wizard, you need to configure the import. First, choose an appropriate way of splitting your document into topics. You have the following four options to choose from: 
    Style outline level (Heading 1, Heading 2...) - a new topic will be created with each Heading specified in the document. Different levels of Headings will become parent and child topics respectively.
    Paragraph outline level - topics will be defined by the outline levels specified in the document's paragraph settings. The hierarchy will be preserved.
    TC fields - topics are defined by TC fields (special invisible elements used in the Microsoft Office to define Table of Contents) of the MS Word document .
    Import as a single topic - the whole document will be treated as one topic.

    Information Don't forget to specify the Max outline level. It will influence the number of TOC hierarchy levels ClickHelp will create.
     
  • Choose the way ClickHelp will handle Styles in your MS Word document after the import. The three options are available:
     
    In the dialog itself, you can read some basic information about those three options. To get more in-depth information, check the Handling Content Styles help topic.
  • If you chose importing the document into an existing project, this settings page will have one more drop-down box allowing you to pick the way the Imported Styles are treated - whether they are copied to a new style file or to a file existing in the project:
     
    Information Note that CSS classes are created for all the imported styles. The names of the CSS styles represent their encoded attributes (for example, for the bold font, the class name is cs0719DCD37).  This means that two CSS styles with different names but with the same attributes will be detected and reduplicated. For this to happen, we strongly recommend using the Existing style file and Optimize styles options, especially, when uploading multiple documents into one project, as the style cleanup is performed and duplicated styles are handled.

  • Check Generate CSS classes if you want inline styles from the imported project copied to a CSS file, and CSS classes created with automatic names for repeated classes.

  • Click Next and proceed to the third wizard step where the import itself is performed.
  • Click Next to get to the finishing step. You'll see the window containing links to your imported project and styles.
  • Click Finish.

Following these steps, you will successfully import any amount of documents into your user manual having it perfectly structured and styled right at the import.

Learn more about MS Word import specifics in this section: