Naming Slices - Second Level Lesson

If you decide to slice up the opening screen and second level page for the same client, a potential problem awaits you. What if you name the slice for the logo on the opening screen "logo" and the slice on the second level pages "logo"? When ImageReady slices up the opening screen, it will create an image called "logo.gif" and place that file in the images folder.

Later on, when you slice up the second level mock up, if the logo slice is named "logo" ImageReady will create another file called "logo.gif" and ask you if you want to replace the old logo.gif with the new file. this is a bad sign.

Here are the 2 logos from the campus and optional sites, as you can see they each have a distinctive look, different size, and need unique names.

I recommend you analyze the images on the opening screen and those on the second level. Any images that are EXACTLY the same on both pages should have the same name assigned to their slice.

For example the navigation However if you have a large version of the logo on the opening screen, and a smaller version of the logo on the second level page you need to distinguish between the 2. I usually name the slice on the opening screen "logo-index" or "logo-home". I save the name "logo" for the second level pages, since so many more of them will be created.

If you slice up your pages and find that you have unexpected images appearing on the home page, it is probably a slice name overlap. some students attempt to solve this problem by creating separate directories for the images used at the home page and those used by the second level pages. This solution works, however if these pages share images, then 2 copies of these images will be created, which is a waste of server space.