Images, Regular vs Site, and Warehsouing, please explain or

New to Rapidweaver, someone told me to learn about regular vs site vs warehousing images, BEFORE I make lots of pages. Do you know WHERE I can learn these differences, or can you take a moment and explain? (Then turn your explanation into a posted, indexed, web page for the future learners!:slight_smile: Thank You ! Weave Onā€¦:grinning:

http://forums.realmacsoftware.com/search?context=topic&context_id=29380&q=Warehouse&skip_context=true

Found it by searching already, reading it right now.

Older versions of RapidWeaver had issues storing and managing resources. RW8 reworked that process.

Warehoused is RapidWeaver slang for storing and managing resources on a web server manually(outside of RW). Many old time RW users adapted using ā€œwarehousedā€ images to get around the older (pre RW8) resource issues. It also has advantages in being able to add/change images outside of RW.

Stacks 4 introduced a new stack called ā€œsite imagesā€. This only works with Rw8 and the reworked resource manager. This allows you to ā€œdrag and dropā€ images into a stacks page once and reuse the same image in multiple places. This is the new default image stack for stacks pages. The ā€œregularā€ image stack is the old style (pre stacks 4 and RW8) image stack, itā€™s there mostly for backwards compatibility, but has some edit features that arenā€™t in the new ā€œsite imageā€ stack.

From a published performance side, any image you put on a website is a separate html entity. If you drag and drop the image onto a RW page, it will still be a separate <img> html element when you publish your site. If the same image is used on more than one place then the new site image or warehoused images could be faster as they would be read from the browsers cache the second time.

Edit and Preview should be faster using the new site image stack over warehoused. Site images are stored locally on the hard drive within the project file were warehoused images will need to be loaded over the internet.

Thank you SO MUCH for that poignant answer! You cut to the chase, and give me what I need. For my size and because of what date it is, where RW is at, in version 841, site images is fine. Although reading about warehousing gave me ideas on how to get more use out of my website and FTP (backup resource). I really thank you for taking the time to answer. Iā€™m sure others will benefit from your answer too.

Anything you put in Resources(like site images) are published to a directory(folder) called resources in the root directory of the site.

RapidWeaver will not delete anything. Thatā€™s a good thing IMO, but if you delete anything from Resources after you publish the site, the images will still be out on the server until you manually delete them with an ftp client or the hostā€™s file-manager. They wonā€™t hurt anything (like slow down the site) just use up space.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.