What Approach do you think is better? (for customer image gallery)
i'm quite new to umbraco, built 2 sites with it, and i know that there is no "correct" solution always - sometime there is several ones.
but still, what do you think, about the pros and cons of this situation:
lets take the gallery example:
1. i have the option to let the user choose folder - and to display all the media items under this folder. (after the user add the media items to pre-defined folder)
2. i have the option to use the custom repeatable content - and let the user add in table (matrix) all the media that he wants.
3. i have the option to let the user create content node of type gallery and add under this node image items. (like in cws2 package).
what approach do you prefer to work with? which option do you and your clients find most easy?
Persoanlly I like option 1. It's really powerful when you combine it with the zip upload package for the media library. Creating a gallery of 100 images might only take 2 minutes using this method.
However, it depends on the exact nature of the galleries as to which method is best. Option 2 looks good (I've never used it) if there is a set of images, which the client wants to show different selections thereof on different pages. Option 3 is good for really dumb users, where there will be a low number of images per gallery, and they won't ever be used elsewhere. I used this one for product screenshots on a software website.
This really comes down to if the images have any data to be attached to them.
For example do they need a image title, description etc. if so then you need to probably go the CWS route or you can add extra properties in the media library itself.
Going the CWS route would give you more control as you can also sort the images per gallery (if one image is used in various galleries) you can also allow/deny access to create galleries based on login, allow update notifications etc.
If it's purely images then option 1 looks good.
The best option would possibly to write a zip upload package that allows you to select a node to add all the images as nodes as in CWS on import, but probably going too far, would be useful though :)
thanks for the opinions - i guess there is no one "right" solution -
using the zip upload and the first option (let the user choose folder) - its simple and nice solution that fits for images without any additional information (like homepage slider etc.).
i found that using the repeatable custom contetn datatype is nice solution and you can include additional info about the images, yet, its good for 20-30 items (that includes additional info). more than that is option but in the frondend it become not so nice and manage items in categories is not nice also using this datatype.
the CWS approach is also good and i think its the best solution if you have many items that need to include additional info and put items in different categories. (like CWS gallery).
Thanks for your opinions and if you have more ideas i will be happy to hear.
What Approach do you think is better? (for customer image gallery)
i'm quite new to umbraco, built 2 sites with it, and i know that there is no "correct" solution always - sometime there is several ones.
but still, what do you think, about the pros and cons of this situation:
lets take the gallery example:
1. i have the option to let the user choose folder - and to display all the media items under this folder. (after the user add the media items to pre-defined
folder)
2. i have the option to use the custom repeatable content - and let the user add in table (matrix) all the media that he wants.
3. i have the option to let the user create content node of type gallery and add under this node image items. (like in cws2 package).
what approach do you prefer to work with? which option do you and your clients find most easy?
Thanks for your time!
Eran.
Persoanlly I like option 1. It's really powerful when you combine it with the zip upload package for the media library. Creating a gallery of 100 images might only take 2 minutes using this method.
However, it depends on the exact nature of the galleries as to which method is best. Option 2 looks good (I've never used it) if there is a set of images, which the client wants to show different selections thereof on different pages. Option 3 is good for really dumb users, where there will be a low number of images per gallery, and they won't ever be used elsewhere. I used this one for product screenshots on a software website.
/Josh
This really comes down to if the images have any data to be attached to them.
For example do they need a image title, description etc. if so then you need to probably go the CWS route or you can add extra properties in the media library itself.
Going the CWS route would give you more control as you can also sort the images per gallery (if one image is used in various galleries) you can also allow/deny access to create galleries based on login, allow update notifications etc.
If it's purely images then option 1 looks good.
The best option would possibly to write a zip upload package that allows you to select a node to add all the images as nodes as in CWS on import, but probably going too far, would be useful though :)
Rich
thanks for the opinions - i guess there is no one "right" solution -
using the zip upload and the first option (let the user choose folder) - its simple and nice solution that fits for images without any additional information (like homepage slider etc.).
i found that using the repeatable custom contetn datatype is nice solution and you can include additional info about the images, yet, its good for 20-30 items (that includes additional info). more than that is option but in the frondend it become not so nice and manage items in categories is not nice also using this datatype.
the CWS approach is also good and i think its the best solution if you have many items that need to include additional info and put items in different categories. (like CWS gallery).
Thanks for your opinions and if you have more ideas i will be happy to hear.
Eran.
finally i marked Josh comment as a solution, to close this topic (and on the way give him little bit good karma.. )
Eran.
is working on a reply...