On 3/9/2016 3:03 PM, Art Campbell wrote:
Yves, I helped John put together his solution, and while Salesforce may use
DITA for its own doc, to import into the Knowledge product (this is not the
parent Salesforce product), you have to package the content in a suitable
format for importing into a proprietary database using well formed HTML and
package it in small chunks, with a CVS map file, into a ZIP that the
Knowledge import tool can parse.
It isn't anywhere nearly as easy as just picking the right standard to
adhere to and to which to prep the documentation unless you're writing in a
database-based system already.
It can be done, and John's solution is as elegant as it's likely to get...
but it's still a lot of hoops.
Oh? I'd be interested in learning more about it.
The real solution is to lean on Adobe to support database export or a
database CMS such as WordPress as a Publishing target.
Or try dropping by an ePublisher Study Hall session and we can take a
crack at it.
Ben Allums
[email protected]
512-381-8885
_______________________________________________
This message is from the Framers mailing list
Send messages to [email protected]
Visit the list's homepage at http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to [email protected]
