Warehousing Images - best way?

Classic General
8

I cannot imagine building a site without using warehoused images unless I wanted to:

  1. Enlarge the size of my RW file and slow down loading, saving and Publish times
  2. Slow down the loading of sites with duplicate images or icons by not taking advantage of browser caching
  3. Lose track of the name of images loaded into RW
  4. Prohibit me from using minuscule sized razor sharp SVG images
  5. Prohibit me from live editing multiple SVG images using only a text editor
  6. Making quick backups of all images used in a site
  7. Edit multiple similar images in RW or live by making one change
  8. Make quick changes in published sites (preview or edit also) by swapping out one image and not needing to Preview again.
  9. Speed up development and prototyping time.
  10. Improve SEO by naming images

The list goes on and on. If none of that is interesting, then avoid warehousing.

In about 18 months of using warehoused images with RW I have never found a draw back or problem and all you need is an FTP program and can even use the free CyberDuck FTP App. Further, I avoid any stack that doesn’t support warehousing.

7 Likes