![]() ![]() One solution may be to save the logo out as a transparency, but what if that's not an option? Because in some situations it won't be an option for one reason or another. If you crop the logo out of the design and you're just one pixel off, it will show because the gradient will not match up. In order to have the gradient line up when the logo is replaced, you need to know exactly where the logo image sits on the background. This can especially be troublesome if the logo sits on a gradient background. This should be a simple change and will be if there is a design file with a slice path for the logo graphic. A basic example of this would be that the company logo has been updated and the new version of the logo needs to replace the current logo image on the site. I have had to make updates to websites that required updating the graphics. There are bigger issues than simple file organization and naming. The Old Photoshop "Crop & Undo" Doesn't Cut It This really isn't an option, at least it shouldn't be. Trust me, it always helps to find things in the file if the layers, groups, and slices are well organized and named accordingly. Some design files can have 80+ layers containing hundreds of graphics and things can get pretty complex. Just because you know how everything works in the design file, does not mean when the client asks for a change months later that someone else will be able to come behind you, open the file, and be able to clearly discern where everything is and how it's organized? Will you remember months down the road? I can tell you from experience that if things are not organized and named well in a design file, the answer to that question is an emphatic "No". It wastes a lot of time and can be very frustrating. Trying to sort through it in order to make a simple update is like a guessing game. In the past, I have had to deal with badly organized design files where nothing is in any particular order, nothing is named appropriately, and there are no slices. Let me start off by explaining the bigger picture a bit and why this issue is worth writing about in the first place. To Slice or Not to Slice: What's the Big Deal?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |