Documentation Respository
Posted: Wed Jan 04, 2017 11:47 am
Hey everyone,
I am looking for some suggestions. We have a Documentation Repository available to everyone in the company. It is currently stored on Confluence and is a single page with links to Release Notes, and any form of Guides that we put together. The guides are currently small and created in Word.
The problem I am looking for a solution to is that several documents in the repository have similar if not the same images in them. I was thinking that if I can create the documents in Flare and link to the same image, I will only have to update the image once. The problem with separate images besides having to keep the screenshots up to date, I don't know which images are in which documents. I would literally have to scan through all documents to see if a similar image is used.
Is there some way Flare can help me in this mess? I was thinking about maybe adding tags to documents so I know which part of the software is included in a particular document. Then I could just look for all documents with a specific tag. This sounds like a lot of work and mess also.
Would love to hear any ideas you may have to organize a documentation repository.
Thanks.
Pam
I am looking for some suggestions. We have a Documentation Repository available to everyone in the company. It is currently stored on Confluence and is a single page with links to Release Notes, and any form of Guides that we put together. The guides are currently small and created in Word.
The problem I am looking for a solution to is that several documents in the repository have similar if not the same images in them. I was thinking that if I can create the documents in Flare and link to the same image, I will only have to update the image once. The problem with separate images besides having to keep the screenshots up to date, I don't know which images are in which documents. I would literally have to scan through all documents to see if a similar image is used.
Is there some way Flare can help me in this mess? I was thinking about maybe adding tags to documents so I know which part of the software is included in a particular document. Then I could just look for all documents with a specific tag. This sounds like a lot of work and mess also.
Would love to hear any ideas you may have to organize a documentation repository.
Thanks.
Pam