Skip to main content
Import content from Paligo CMS by uploading a Paligo XML export. The connector converts DocBook 5.0 XML to Markdown, preserves the topic hierarchy, and stores all referenced images.

​
Prerequisites

  1. Access to a Paligo CMS workspace
  2. A Paligo XML export (with images) uploaded to the server

​
Exporting from Paligo

  1. Go to your Paligo publication
  2. Select Publish
  3. Choose XML as the output format
  4. Ensure Include images is enabled
  5. Download the ZIP file
The export contains a publication--[lang].xml file (e.g., publication--en.xml) and an image/ directory with all referenced images.

​
Setup Steps

  1. Upload the extracted Paligo export to a directory on your server
  2. Navigate to Knowledge > Sources > Create
  3. Select Paligo as the connector type
  4. Enter the directory path where you extracted the export
  5. Optionally specify the XML filename (defaults to publication--en.xml)
  6. Save and run a manual sync

​
Configuration

​
Multi-Language Documentation

Create a separate source for each language. Export each language version from Paligo and point each source to its own directory and XML file.

​
What Gets Imported

​
Topics

Each section with a resource ID in the Paligo XML becomes a separate document in AGO. The hierarchy is preserved: nested topics maintain parent-child relationships, while sections without resource IDs become sub-headings within their parent topic.

​
Content Conversion

The connector converts DocBook XML elements to Markdown:
  • Paragraphs, headings, and inline formatting (bold, italic, code)
  • Bullet and numbered lists (including nested lists)
  • Procedures (step-by-step instructions)
  • Tables (with multi-line cell support)
  • Code blocks with syntax highlighting
  • Admonitions (notes, warnings, tips, cautions)
  • Sidebars and accordion elements

​
Images

Images from the export are stored as attachments on the corresponding documents. The connector searches multiple directories (image/, images/, img/, assets/images/) to find referenced images.

​
Best Practices

  • Test with a small publication first before importing large documentation sets
  • Re-export and re-import periodically to keep content fresh
  • Optimize images in Paligo before exporting to reduce storage
  • Use absolute paths for the directory path

​
Troubleshooting

  • Verify the directory path is correct and absolute
  • Check that the XML file exists in the directory
  • If using a custom filename, verify it matches
  • Ensure images were included in the Paligo export
  • Verify the image directory is named image/, images/, img/, or assets/images/
  • Re-export from Paligo if image files are empty or corrupted
  • The default maximum nesting depth is 10 levels — deeply nested content beyond this is not imported
  • Consider restructuring overly complex content in Paligo
  • The connector automatically detects and skips duplicate resource IDs
  • Check your Paligo publication for duplicate topic IDs