Live data from Hacker News

PSD to HTML is Dead

blog.teamtreehouse.com

71–80 of 171 posts

Re: PSD to HTML is Dead

#71
post #26

And thank goodness. If anybody knows where the grave is, I'd like to go piss on it. As somebody who long ago did print design, I totally get why designers would want pixel-perfect control. It is awesome, but you get that in print because you are physically manufacturing an object and sending it to people. The web was device independent from the get-go. It wasn't your paper anymore; it was their screens. There were a…

Before the casket is closed, I'd like to throw 'spacer.gif' in there with it. I don't think even the Pope can absolve me of that sin.

Re: PSD to HTML is Dead

#73

Rant to follow: So I have done a fair share of PSD to HTML, PSD to WordPress theme, PSD to application web GUI, etc. rewrites. I generally have no problem with the concept of this, and got quite good at this. However, there are some real pet peeves that keep coming up in this workflow, that are really driving me crazy. If you are a designer working with a developer, and you happen to read this, at least please consid…

This kind of work has been a large part of my job for a long time, and I definitely recognize all of those frustrations. This may be obvious, but the problem is usually not a lack of communication but rather that the designer/client/manager isn't able or willing to think through the design fully. As such, when you seek clarification on something, you're really asking the stakeholder(s) to figure it out for the first time.

I've learned that a good strategy is simply to figure it out for them and hand it back complete. Not only does this eliminate communication overhead, it allows me to pick a solution that strikes a good balance between quality and my own time and effort, as opposed to having to push back against some half-baked, unrealistic idea.

The vast majority of the time, whatever I come up with is accepted either without comment, with minor requests for tweaks, or with elation. In the rare instance that something needs to be redone from scratch, I've at least gotten the ball rolling and given the stakeholder(s) some idea of what's possible.

It's kind of like turning a waterfall process into an iterative one by doing the first iteration yourself.

Re: PSD to HTML is Dead

#74
post #33

Earlier quoted context omitted.

Great point. Does anybody know the historical origin of the notion that there are "designers" who can be ignorant about their medium? When I talk to, say, friends who paint, it's a very specific activity for them. They know a lot about actual paints, because they do the painting. Pre-web, I knew people who were print designers, or packaging designers, or logo designers. They too knew the details of their medium intim…

Design as an profession is older than the web - it's older than programming. The industry as a whole is intimidated by modern technology, and appeals to non-technical people. As a result, many of the people coming out of professional design schools, trained in the esthetics of flat, non-interactive design see themselves as 'above' all that 'computer stuff'. This, combined with intimidation, and a massive demand for g…

> As a result, many of the people coming out of professional design schools, trained in the esthetics of flat, non-interactive design see themselves as 'above' all that 'computer stuff'.

I feel like this doesn't happen so much anymore. At least from recent graduates of top NYC design schools, you'd be hard pressed to find a communication designer / graphic designer who isn't worried about having to learn HTML/CSS because "print is dying".

Re: PSD to HTML is Dead

#75
post #54

What is the best HTML page design tool? I.e., designing CSS and HTML with minimum coding?

Webflow (https://webflow.com) is made precisely for this. To get a feel for what it's like, have a look at the playground: http://playground.webflow.com/ (I'm one of the founders.)

Re: PSD to HTML is Dead

#76
post #26

And thank goodness. If anybody knows where the grave is, I'd like to go piss on it. As somebody who long ago did print design, I totally get why designers would want pixel-perfect control. It is awesome, but you get that in print because you are physically manufacturing an object and sending it to people. The web was device independent from the get-go. It wasn't your paper anymore; it was their screens. There were a…

Hear, hear. I'm ashamed to admit I built one or two websites this way - but then I got a job wrangling XML into EPUB, and oh my word am I sorry for my sins now.

And this:

>It wasn't your paper anymore; it was their screens.

...is something the publishing industry needs to, but seems to be pathologically unable to, appreciate.

Re: PSD to HTML is Dead

#77
post #14

I'm a little bit confused of the workflow they are suggesting. I'm a web developer with "good design taste" but I definitely can't design myself, I always pair up with a designer that does the PSD. But of course this doesn't mean that when I see a navbar that has a gradient I copy a paste the image of the navbar in my website with a , my job is porting this images to HTML, CSS and JS. If you're actually putting image…

this doesn't mean that when I see a navbar that has a gradient I copy a paste the image of the navbar in my website with a

At one point in time you couldn't do gradients in CSS, so that's exactly what you did. Luckily, that era is over.

Re: PSD to HTML is Dead

#78
post #17

Earlier quoted context omitted.

"Nine out of ten times I want to do something with CSS I prefer doing it with JavaScript" You're doing something wrong then.

center a div both vertically and horizontally to the viewport; also it should stay center when resized.

Although this used to be a problem with CSS, it has been fixed in modern browsers: http://philipwalton.github.io/solved-by-flexbox/demos/vertic...

Re: PSD to HTML is Dead

#79
post #52

PSD to iOS as well. I just wish companies would stop wasting resources on photoshop goons and let the engineers who work with the platform & SDK design.

I'm not sold here on this one. Since we know the specific small set of resolutions on iOS devices, I'd rather have a designer/UX lay down exactly how it should look, then have devs execute on that. If dev provides a valid reason why a design component would be a royal pain, then design can go back and adjust.

Just had this argument 20 minutes ago on using a native control versus designing our own and adding a few listeners - which has a better look and experience.

Background: taught a PSD to HTML college course; stopped doing PSD-HTML myself about two years ago; still favor PSD-iOS

Post reply on HN