I got it to work. This is really cool. Thank you.
What I couldn’t figure out was where should I create/add the assets folder. I couldn’t figure out if it should be in the same hierarchy as ‘html’ and ‘cgi-bin’–or should it be in html/files/assets or somewhere else.
For others who follow this thread–or find it–here’s what I did.
Per Paul’s advice, I added a new folder within the ‘html’ folder and named it “assets,” from there I dropped the images I want to warehouse into the assets folder.
I started out by testing just two images.
Thank you Paul for clearing this up.
However, at the same time, even after I created html/assets/logo, when I right clicked in Yummy FTP for Copy As URL, what I got back was ftp://myusername:@atmyspecificserver.com/html/assets/logo.png, where myusername was my actual username and at myspecificserver was actually my specific server.
Still in Yummy FTP, A right click request for ‘Copy As Web URL’ yielded http://mywebsite.com/html/assets/logo.png, but that URL just went to a web page that said:
The requested URL /html/assets/logo.png was not found on this server.
Finally, I took the ‘html’ out of the URL address. Bingo. http://site.com/assets/logo.png
This is so great, and I think this is something that should be built-in to RapidWeaver.
Here’s the real beauty of this method–in my opinion.
- You can rename your images to something/anything search engine friendly.
In my 2nd example screenshot, with the red arrow pointing to the assets folder, the second image is a stacks image that shows up on maybe 40 pages on my site. The stacks image was named “stacks-image-3c5p5d9.png” by RW/Stacks. That’s not an SEO-useful name, but buythisproductbecauseitsgreat.png is useful.
This is huge.
- You can dramatically reduce the size of the site itself since one 12 kb image that appears in 100 places will still only require 12kb–instead of 100x 12kb images–that each have to load separately.
This improves the site loading speed exponentially.
- Since google now ranks mobile-friendly sites higher–and concurrent faster loading speeds as still another reason for giving such sites higher rankings, this is an area that RapidWeaver can really capitalize on and should.
Thanks again Paul for your clarified instruction.