We use structured FrameMaker. We have a mature EDD, we are happy with the way things are.
But it's not really any closer to single source, or modular documentation, as we still have the content stored in .FM files and organised in books. However, trying to find out the best way to store the documentation, so it will be properly modular, is proving tricky (of course, it may just be my interpretation and understanding that is lacking). Does anyone store their content in a database? Or as XML? How re-usable is your solution? We have a lot of similar areas of our product, and I want to make the best use of the existing content but at present it's still a lot of cut-n-paste which is not good. Where am I going wrong? Gordon __________________________________________________ Publications Team Tel: 01415334164 ____________________________________________________________________________________________________ This email (and any attachments) is private and confidential, and is intended solely for the addressee. If you have received this communication in error please remove it and inform us via telephone or email. Although we take all possible steps to ensure mail and attachments are free from malicious content, malware and viruses, we cannot accept any responsibility whatsoever for any changes to content outwith our administrative bounds. The views represented within this mail are solely the view of the author and do not reflect the views of the organisation as a whole. ____________________________________________________________________________________________________ Graham Technology plc Registered in Scotland company no. SC143434 Registered Office India of Inchinnan, Renfrewshire, Scotland PA4 9LH http://www.grahamtechnology.com ____________________________________________________________________________________________________
