Doxygen integration seems like the biggest no-brainer decisions the Confluence team could make.

Just wanted to +1 this feature request.

We have a lot of users with auto-generated HTML content (Doxygen, etc) and they would prefer to be able to import an entire HTML tree (including images) into Confluence as a set of pages without needing to use the Universal Wiki Converter or any other external tool or plugin or add-on for Confluence.

So, there is this Import Tool, which allows to import simple HTML into a space (Space administration > Import). Here you can import a folder containing several HTMLs from the server. BUT there are a few problems which effect me (probably even more that don't):

• Hyperlinks are mostly broken
• Page hierarchy is not maintained

I want to upload around 300 pages of html on a regular basis. Fixing the hyperlinks and hierarchy manually each time would just take to long. Can we hope to see this feature anytime soon?

I don't know how this wasn't a feature from the start. The number of people with HTML skills vastly outnumbers the people with wiki markup skills.

For us updating through an import process reduces a multitude of issues related to accuracy, reliability, uptime, and productivity.

Our current Wiki is updated hourly by employees across the world and consists of hundreds, if not a couple thousand pages. Importing manually means that we have to stop user productivity and allocate resources (we don't have) to import as much as we can while keeping track of changes that happen during the manual import process. All of this becomes to complex to organize and track, and coordinate with our users.

By creating an import tool that allows the hyperlinks, page references, images, and code to import reduces inaccuracies and would allow us to complete the task over a weekend with minimal downtime to our end users. We are a global company and do have users reference our old wiki even on the weekends. So, asking users to suspend changes over a weekend is far more tolerable than our current prospects which point to a drawn out process.

agree, this should be a no-brainter to provide this functionality for people looking to migrate their older wiki's into Confluence; we have the same issue. To do this manually would be exteremely time consuming.

We are currently evaluating Confluence, but find it not very useful when it comes to migrating the HTML help files that we have created. Is there an easier way to import HTML to Confluence the same way we import Word documents?

My company would also see this as very beneficial. We have a number of wiki/content management systems and it would be good to have this all imported into Confluence.

(1) I vote YES, for this feature.
(2) My company is thinking of buying Confluence.
(3) See my related posting, here ... ( https://answers.atlassian.com/questions/28193/migration-process-for-single-html-export-of-existing-wiki-and-single-import-using-an-unknown-bulk-import-command )
(4) Thank you.

Seems there's an aussie company providing this service as a plugin for MS Word. Licence starts at 40US$/year. check it out.
http://www.hiason.com.au/

<quote>
Hiason provide a custom data conversion service for converting documents to wiki markup, and loading the data directly into your Confluence wiki. If you have an intranet of HTML pages, lots of office documents, or documents in other formats, contact us today for further details or a quote.
</quote>