After importing the CloudForms topics, I ran through the process of converting their "Cloud Engine User Guide" into a CSP map. The end result of this can be see at http://file.bne.redhat.com/~mcaspers/Cloud_Engine_User_Guide/tmp/en-US/html-single/, which is built from CSP Map 9920.

Unfortunately this conversion process has to be largely a manual process. The CloudForms documentation was a mix of structure and content i.e. text that belonged in a topic (and indeed has to be in a topic to be used by Skynet) was quite often found in the parent XML files. I think this is an issue with the TopicTool, because it seemed that quite often images were not included in the CloudForms topics, although with some other edge cases. Converting this documentation for use with Skynet, where content is strictly seperated from structure, had to be done by hand.

What this means is that there is little point creating a tool to map <xi:include>s to injection points or CSP maps because the amount of work it would take to create such a tool would not be reflected in the amount of work that is saved in the conversion process.

(In reply to comment #1)
> Unfortunately this conversion process has to be largely a manual process.
> The CloudForms documentation was a mix of structure and content i.e. text
> that belonged in a topic (and indeed has to be in a topic to be used by
> Skynet) was quite often found in the parent XML files. I think this is an
> issue with the TopicTool, because it seemed that quite often images were not
> included in the CloudForms topics, although with some other edge cases.

It's not clear to me what the issue with Topic Tool is here, do you have an example? Topic Tool uses the same container for topics (section) and supports the use of images within them...of course if users didn't use that functionality then that's another matter ;).

Closing this as this is being taken on by Dan Macpherson.