Organizing content-related images

[tachyondecay]

I created a assets/img/screenshots/ for holding any screenshots we use in our docs, rather than cluttering up the parent directory with content-related images. We should probably create other folders for different types of images, if we need them.

Within that directory, I created a subdirectory for the version of Symphony shown in my screenshot. This way, we can see at all times how many screenshots we have from each version, so we'll know if we need to update something when the user interface changes.

[bernardodiasc]

My previous experience with a big tutorial, with about 30 screenshots, say that having a folder exclusively for each content is a good thing in long term. Imagine 10 tutorials like this, with more than one system version.

[tachyondecay]

That’s a good point.

Do you think we should adhere to a folder for every doc? I’m not crazy about creating a folder if I'm just adding a single screenshot—or if the screenshot I’m using is so general I want to use it in more than one place.

Maybe we should have assets/img/screenshots/<version> for generic screenshots, and assets/img/screenshots/<tutorial> for specific tutorials that require a lot of specific screenshots?

[bernardodiasc]

sounds great. +1

@johnpuddephatt what your thoughts about this? would be nice to have another opinion on this :)