Getting Started with Paligo

Table of Contents

Using the Import Wizard

The import wizard can directly import DocBook 4.5, DocBook 5.0, HTML and Paligo Export Format. By an indirect procedure, pre-converting to any of these formats, you can import a number of other formats as well, for example DITA, and even proprietary formats such as Confluence (HTML Space Export), Microsoft Word, MadCap Flare and Author-it, etc. 

To import DocBook, HTML or Paligo Export Format, do as follows.

  1. Put the content you want to import in a folder on your local hard drive.

  2. For plain HTML, XML, or DocBook imports, make sure you have only one import document in the root of that folder. E.g, if you are importing HTML, make sure you just have one "index.html" in that folder. If importing DocBook, have just one DocBook document in that folder. The images and other resources may be in sub folders, as long as the image links are not broken. See the image for an example of what a typical HTML folder might look like.

    Note

    Special instructions apply to some formats, such as Confluence, which can have multiple HTML files in the folder. See the specific instructions for each format.

  3. Zip the folder.

  4. In Paligo, create or select a folder where you want to import your content.

  5. In the context menu, select Import content.

  6. In the wizard, select the input format that you are going to import, and select the zip file you created with your content. Click Ok.

  7. The import will start. Depending on how much content there is in the zip file, it might take anywhere from 10 seconds to several minutes.

Smart import

Paligo will automatically detect if several of the sections in your content are identical, and then not import it again, but instead reuse the topic already imported.

Note

If you get any warnings about incorrect structure when you try to import, such as saying that a para cannot contain a list or the like, try checking the checkbox "Ignore warnings on import". Paligo will then attempt to fix those incorrect structures during import instead. 

When the import is done, your documentation should have been divided into topics, and you should have a Publication/Project with these topics reused in the same structure as the content you imported.