: Organizing PSDs for developers Is it ok for designers to not organize PSDs before giving them to developers? If not, how do you prepare your PSDs for developers? I'm asking, from the perspective
Is it ok for designers to not organize PSDs before giving them to developers? If not, how do you prepare your PSDs for developers?
I'm asking, from the perspective of a developer.. the designers I work with always provide me with PSDs that are huge. Layers are scattered all over the place, and I spend hours sifting thru smart objects and layer masks trying to find the elements I need to cut out.
I've attempted to communicate to them that I'd really appreciate if they would even simply just delete layers they're not using, or group layers together so I'm not trying to find things because 1 layer which corresponds to another layer is in totally different folders in totally different places.
I even went so far as to take one of the layer comps that they gave me, and organized it in a way that I thought would be reasonable.. It was disregarded.
More posts by @Margaret771
3 Comments
Sorted by latest first Latest Oldest Best
Two resources that might help:
Photoshop Etiquette
PSDCleaner
And then, if the designers and you are part of the company you work for, I'd speak to your boss and explain the amount of time you waste wading through the designers' mess. Maybe he can put pressure on them?
If you are an external contractor, I'd itemize the hours spent on that separately, to also make it clear to whoever is paying the bill that their designers' sloppiness costs them money!
I do not believe a developer needs a PSD file. I say this because web should be coded and not sliced. A developer should be considered just like a printer in regards to receiving a final PDF of the site and a resource folder of the desired images and content that can't be coded. (If a proper sit-down was done than this step shouldn't be an issue). Manipulating someone else's designs can lead to complications and errors. You could accidentally delete or alter something that you haven't caught and will have to step back and redo what you're doing when it comes to a slice.
I know a few people may disagree with my logic but I think you're stepping back in this instance. Why? Because the site is already designed and if you're slicing for responsiveness you're wasting a lot of time, reference:
What are the steps in designing a website?
How can I accurately describe text and image sizes for our iOS developers?
In regards to your workflow I think you need to address this on the front-end. If the designer is contracted out, review the contract. If this is a company and the designer is an employee than I would suggest a sit down with the designers and developers to agree on a desired workflow and collaboration. As mentioned in the comments the industry is always evolving and a successful company cannot execute an archaic workflow like slicing. I would suggest looking into designing in the browser and a mobile first approach but that may be just my opinion.
This all comes down to the work ethic of the designer. It is difficult to force anyone to be organized if they simply aren't by nature.
Is it "okay"? That would depend on your perspective. Obviously it's not okay with you, but it sounds like it's perfectly okay to them.
I personally, name, group, and organize layers of any file. I find it much easier to not only hand off the file if needed, but to edit the file later. And it's much easier to start organized and stay organized than it is to sift through things later.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.