I must admit that I have tended to use image folders in the past, but it may be worth considering the fact that if your going to use nav buttons with 3 or 4 states per button plus all related sliced backgound images ( the ones XX call 13c4l etc) + shims it does make sense to keep each single html page together with it's linked images in one file per page and link each html page to each file. This way it is far easier to delete all files associated with an individual page than if all image files are stored in a single image folder.
As an example if you produce 3 html files each with different nav buttons, all these buttons are called button 1, button 2, button 3 etc. how do you know which button1.gif relates to which html file ? (I know you can get around this by altering the name from "button1" to "home" in the names gallery) but it still does'nt account for the r3c12.gif files that XX produces.
All I'm trying to point out is that maybe it would be better sense from a web design aspect to have one file per page, and link the pages to each file rather than have all HTML pages in a single file and all images in an "image" file. Any common images across all or most pages could of course still be held in an "image" file. I have only kept all my previous images in one single "image" file as this way my web editor has prompted me.
Does this make sense?
Egg
Egg
Minis Forum UM780XTX AMD Ryzen7 7840HS with AMD Radeon 780M Graphics + 32 GB Ram + MSI Optix Mag321 Curv monitor + 1Tb SSD + 232 GB SSD + 250 GB SSD portable drive + ISP = BT + Web Hosting = TSO Host
Bookmarks