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 16:57:06 -0700
It's not rocket science, but I was never able to get it to work. The
project was cancelled, so I never figured out if it was a bug in the
Confluence API or what.
On Sat, May 28, 2016 at 11:42 AM, Mark Baker <mbaker -at- analecta -dot- com> wrote:
>
> Could be, depending on how links are stored internally and whether or not
> you can specify the name of a page when you create it. It you need to use an
> ID assigned by the system then one approach would be to create all the pages
> blank, get their IDs and then update them with the links updated to use the
> provided IDs. More than just an bit of XSLT required to do that, but not
> rocket science.
>
> Then again, some systems do put up barriers, so you don't know for sure
> until you try. It is possible with many tools. Can't say for sure about all.
>
>> The challenge in importing anything beyond a single page into
>> Confluence is preserving the cross-references.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com