Re: STK and images: where to store them?

Hi Matteo

Yes, a very interesting question!

Usually we encourage to store images in the DMS. The main reason is  
that we want to always have authors alter images. Another reason you  
want authors to select images from the DMS is that you can run  
workflows to upload the images to the DMS, making sure copyrights and  
quality are verified. If authors can select from disk, they might  
select uncontrolled or non-legal images.

But when it comes down to design, we separate again. If you have a  
"Creative" team defining the assets, then we usually go for the DMS.  
The "Webmaster" can review and upload images to the DMS. Usually, this  
is the easiest way to replace existing assets.
However, if you have inhouse developers maintaining the layout, for  
them it might be easier if they can just push them into /docroot.

You see, there is no "general best practice". What I though suggest is  
that you base your decision on the processes you have in place. While  
during development it will be easier for the developer to maintain  
layout images in /docroot, deploying from /docroot might be more  
cumbersome than from the DMS, especially once you are in production  
mode.

Cheers
/giancarlo

On Jun 25, 2009, at 5:01 AM, Matteo Pelucco wrote:


Hi Magnolians,
we (our company) have a little doubt about the right place where to  
store layout images on Magnolia 4.1+.

We see 2 main solutions:

1) to place images as usual on /docroot/site-name folder
2) to place images on DMS / DataModule

The first choice implies that for each change we need a filesystem  
access, or we need to use the mgnl module file extraction capability.
The second one implies an AdminInterface access even to change a  
background-img.

The choice is not so obvious, think about STK and CSS/JS: CSS update  
is comparable to background-img update, so why CSS are on STK and  
images not? In other words: background-img is close to template  
definition, so why it is not managed by STK?

Thanks for sharing your ideas and opinions.

Matteo


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------