Importing and Exporting

Desired Features

• space versioning or export by time
  • for documentation, it would be good to have the ability to tag a version.
    • David Valentine exporting is an acceptable version of this. It includes the comments. The ability using a format template is needed to really make it work.
      • Maybe a command, that creates an archive with the exported the space, and html pages.
  • MIKE - One idea we had here (although we haven't explored it much) is the notion of 'tags' (a bit like CVS tags - not to be confused with meta data tags above!) that make a 'point in time'. This way you could perhaps do things like 'navigate the space with a sticky tag set' or 'export all pages with a given tag'?

• It would be helpful to be able to specify the space to import a differently-named space into, using Confluences import and export feature. (As far as I can tell, it is only possible to import a space under it's same name as things stand now.)

Import formats

Work has begun on a Wiki Exporter for various other formats.

• twiki
• swiki
• JSPWiki
• snipsnap since you use radeox under the hood, all my macros can follow.
• FitNess
• MIKE - We can look into these.
• bookmarks.html from Mozilla
• OpenWiki I would like to be able to import our 500 pages to Confluence
• Amaya created pages (h1..h6,ol,ul,etc.) import just about perfectly with just a copy (as viewed from firefox) and paste into the "Rich Text" editor window. No images or links of course.

Export templating

I'm copying the following out of CONF-482 at Mike's request. Please comment and if you feel like it, edit the text to not be in first person! Basically the main usage I see for PDF exports is delivering documents to people outside our company and for that I need to be able to make the docs look like our brand.

If we started using Confluence, we'd need to be able to customize the page templates so that the software looks like our brand. This isn't critical for the web interface (although important for extranet use) but is an absolute must for the page exports, especially PDF exporting. Othervise we can't really utilize the exporting for generating documents for third parties.

Editing the templates should be possible in the web admin without restarting the application so that fine-tuning the template is possible without major hassle. Also the templates should of course be saved with exports (and backups). If the template editing requires the IT admins to edit files on the server used to host Conf with graphic designers, the template editing is next to useless.

It should be possible to have multiple templates and be able to choose among the templates when exporting and possibly on space-basis for the web interface.

I exported some of the documents and spaces to PDF and the templates used strange styles for fonts, odd paragraph spacing etc which resulted in the document taking a lot of extra space and be hard to read.

What I'd like to change is the whole flow of the exported document, maybe by being able to edit the wrapping around each type of exporte element (headlines, paragraphs etc).

I see the website uses CSS styling heavily which would allow the site to be customized by just changing the style sheet (very nice!). Would this approach work for the PDF documents also or does it already use a CSS-like approach for the styles?

export formats

• docbook
• MIKE - Very hard, I'll put it in the 'future' basket ** Dave: Really looking for something to work with maven/forrest. Said docbook, because that's what goes easily into Framemaker, which our technical writer uses. The jira doc is great. Could one export a space in a format to generate such documentation.
• another possible format is APT: almost plain text http://www.xmlmind.com/aptconvert.html

using exported information

• Using Exported HTML in Word