Generally speaking, if an image is used only once on a site should it still be stored in RapidWeaver Resources or is Resorces best really for images used multiple times only?
Neither. Warehouse your images. Most flexible method and cuts down your project upload time when publishing to your server.
This is how - on your server, in your root (public_html) folder upload a folder called āimagesā.
Then for each page of your site have another folder inside called āhomeā and āabout-usā or whatever.
Store the images that correspond to each page in the relevant folder.
When building a project in Rapidweaver choose the warehouse image option and copy the URL remembering to delete the public_html bit.
Done.
I would agree, to a point. What stacks you use will be a big consideration too. Many stacks and some frameworks donāt support āwarehousingā. I would also suggest the size of your projects, not to mention the number of projects you maintain, has a bearing too.
I maintain about 60 or so client sites, and almost all use warehousing. I use a special domain on the same server as the clients site to āwarehouseā the images and categorize the images into folders based on width and type. This way I can use the same image on several different sites.
To maintain the image āwarehouseā I use the brilliant Repository stack from @Jannis https://instacks.com/repositorystack/ Itās far quicker and easier than using an FTP client and adds a lot of additional features. Repository was built for many different uses but I know it was geared towards just this purpose, so itās tools are perfect.
Warehousing isnāt the only way to go though, many use Resources and are very happy with it. Itās horses for courses.
1 Like
Thank you Aidy and TemplateRepo. Great advice that clears things up. I have been trepidatious about adopting a warehousing approach but itās pretty clear that should be my SOP going forward.