TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: integrating authored content with generated API docs
Subject:Re: integrating authored content with generated API docs From:Robert Lauriston <robert -at- lauriston -dot- com> To:TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Sat, 28 May 2016 11:00:53 -0700
The challenge in importing anything beyond a single page into
Confluence is preserving the cross-references.
I presume that's why the several existing plugins that do that kind of
thing all treat the import as an attachment.
On Sat, May 28, 2016 at 10:39 AM, Mark Baker <mbaker -at- analecta -dot- com> wrote:
>> Importing javadoc or Doxygen XML output into Confluence would take
>> more than just a bit of XSLT.
>
> Well, I haven't actually done it, but from what I can see from the
> Confluence docs, using XSLT to convert to Confluence wiki markup and then
> calling the Confluence REST API to add the content seems straightforward.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com