Page 1 of 1

Image repository

PostPosted: Mon Aug 28, 2017 12:43 pm
by Pamb10
Within my projects, I have a lot of common images. My 3 projects create documentation for 3 products with numerous output versions. Along the way, I will be creating Release Notes and other smaller projects. I want to have a single set of product images that are used in the main projects along with release notes and other supplemental smaller projects.

Does it make sense to have a global project that contains all images (like an image repository) and then link it into each project, release note, and others documents that may come up. This would provide a single source for images.

Most of the images I use belong to a specific product but I may be creating a document that shows the images from 2 or more products.

Hope this makes sense....


Re: Image repository

PostPosted: Tue Aug 29, 2017 1:56 am
by ChoccieMuffin
Sounds sensible to me. In my globals project I also include stuff that I want to use in every other project like stylesheets, page layouts, masterpages, copyright text and other common content.

For your images I also suggest you put them in folders (rather than in the default \Resources\Images folder), and condition them per product so you don't end up with absolutely every single image in every project but can apply conditions to your import file.

That's only part of it - see a much fuller suggestion here: viewtopic.php?f=75&t=29434&p=128656#p128656

Re: Image repository

PostPosted: Tue Aug 29, 2017 6:59 am
by Pamb10
Thank you. I do have a question...with regard to your comment about putting conditions on folders containing images. This is something that has always confused me.

So assuming my global project includes these product image folders and I put ProdA or ProdB conditions on them...

In ProdB project, no ProdA images will be included. However, what if I need one of them? Will it be included if I specifically insert it into a topic in ProdB?

Re: Image repository

PostPosted: Tue Aug 29, 2017 8:03 am
by ChoccieMuffin
Pam, see my reply to your other post - I have made detailed suggestions about how we work here, and how you might want to consider for your documentation set. :)