show/hide this revision's text 2 print to pdf is best

There is no simple (or easy) answer

Print to thisPDF We recommend viewing the wiki article in your browser and using print to pdf. There You can adjust your template for the wiki to format it best for printing. On Mac, choose Save to PDF... from the print dialog box. On Windows, grab a free tool such as CutePDF.

Programmatic exports. If you need to export many pages or export programmatically, there are many options, just see this question to get a feeling for how all fairly complexit is. Here are some basics:

  • Wiki articles are stored in the database as raw html - good
  • Intra-wiki and case links are relative - tricky
  • Embedded images and attachments' URLs can be accessed programmatically by adding an XML API logon toke to the end - good
  • If you use plugins in your wiki such as the Table of Contents or other Wikiblock plugins, these only put a placeholder in the HTML which is dynamically replaced on render - tricky

Some things to try:

  • Have your live documentation site use the XML API to pull the article's HTML when the user requests a document on your site. The script on your site would then need to fix relative links. You would also need to make sure the wiki is publicly accessible so images and attachments work, or store an API logon token in the script on your site for fetching them.
  • Spider the wiki either as a user would, or better with the XML API. convert links, etc, apply styles and save the documents in your desired format. See this answer for an outline.

To those who can edit: feel free to add any accumulated knowledge from your own export efforts
show/hide this revision's text 1

There is no simple (or easy) answer to this. There are many options, just see this question to get a feeling for how complex it is. Here are some basics:

  • Wiki articles are stored in the database as raw html - good
  • Intra-wiki and case links are relative - tricky
  • Embedded images and attachments' URLs can be accessed programmatically by adding an XML API logon toke to the end - good
  • If you use plugins in your wiki such as the Table of Contents or other Wikiblock plugins, these only put a placeholder in the HTML which is dynamically replaced on render - tricky

Some things to try:

  • Have your live documentation site use the XML API to pull the article's HTML when the user requests a document on your site. The script on your site would then need to fix relative links. You would also need to make sure the wiki is publicly accessible so images and attachments work, or store an API logon token in the script on your site for fetching them.
  • Spider the wiki either as a user would, or better with the XML API. convert links, etc, apply styles and save the documents in your desired format. See this answer for an outline.

To those who can edit: feel free to add any accumulated knowledge from your own export efforts