I'm trying to find out what are Flare's CMS capabilities in order to design and structure the contents we want to use.
We produce different software tools with some common functions between them (and thus common contents between the different printed guides). At the moment, each development team (and the technical authors for each tool) work like islands. We have user guides written in Word and we want to start using an authoring tool. So we would transfer all the information in these manuals to the authoring tool and use it also to create context sensitive online help.
Let’s say that we use Flare's capabilities to have some simple content management system. The idea would be to place text and image elements (sometimes a whole topic, sometimes something as small as a paragraph or even a sentence) in a common porepository in an unstructured way. Then the authors would retrieve these unstructured elements to structure their documents or online help projects. But the only way to make this properly work is to tag all those pieces of information. For retrievability and reusability purposes, I would need to tag each element (maybe with metadata?) so that people know:
- * To which software tool is the element associated
* What is the intended audience of the element (engineers, normal users, etc.)
* What kind of help is the element providing (user guide, reference material, installation guide, marketing, etc.)
* For what kind of output is the element intended for (online help, printed manual, training material, etc.)
* Etc.
TIA,
Dnaiel