31–40 of 52 posts
What is needed I think is some sort of visual design tool, maybe not full WYSIWYG which respects and understands template languages rather than bulldozing everything.
IMHO, frameworks such as Bootstrap would fit your definition of WYSIWYG pretty well.
A designer I work with hands me AI files that I'm then meant to convert to a WordPress theme. She knows near zero about coding. It's a nightmare and I'm constantly in battle of functionality and her wanting things pixel perfect. The worst is that she hands over the designs to the clients who do not understand that it will not be pixel perfect and many things will change.
Earlier quoted context omitted.
IMHO, frameworks such as Bootstrap would fit your definition of WYSIWYG pretty well.
What I'm thinking of would be a visual editor that works with things like bootstrap.
This is a high-brow flame war. The last post bothered me, and this one bothers me all the same. Let's cut the shit for a minute and examine the lay of the land. "PSD to HTML is dead" panders well to developers. But it doesn't make it true. Let's dig a little deeper into why a developer may want to believe that the incredible toolset contained within Photoshop is completely useless and unnecessary: The inability to us…
I know I would personally prefer to work where I have some sort of "from designer" reference point. Be it scribbles on paper or a PSD, don't know if I care.
Says the company whose entire business model is built around PSD to HTML conversion. Sometimes one works better than the other for a project's specific needs. And vice versa. What we are needing to get past is pixel-perfect design, however.
This is a high-brow flame war. The last post bothered me, and this one bothers me all the same. Let's cut the shit for a minute and examine the lay of the land. "PSD to HTML is dead" panders well to developers. But it doesn't make it true. Let's dig a little deeper into why a developer may want to believe that the incredible toolset contained within Photoshop is completely useless and unnecessary: The inability to us…
I agree with most of your points except this:
>>Moving divs around, adjusting CSS or erasing pencil off a piece of paper is never going to be as efficient as clicking on a layer and moving, resizing it, etc.
As a visual designer and front-end developer (that knows Photoshop very well), code is actually far more efficient for modern UI's. It's much better organized than the PS layer model, CSS gives you tremendous reach with your changes (especially with SASS/LESS), and Developer Tools (or Firebug) give you amazing reactivity.
However, that being said, the designer must have both design skills and coding skills, which aren't, and shouldn't both be a requirement for the position. The most creative and best graphic designers tend to not know code well enough to become more efficient with it than their traditional layout tools.
The best middle ground for "thinking for UI" and quality graphic design is Sketch. Sketch eliminates 80% of the stuff you never use in PS for web design and adds the features you didn't know you wanted. Its styling options reflect the styling options of CSS. I can't recommend it highly enough.
Honestly, unless you have some very complex personnel issues, every web designer should be using Sketch over Photoshop (and maybe use Photoshop for image manipulation).
I would not hire one translator to translate from Russian to English, when the Translator only barely understands English, and one other second translator who Fixes the first translators work.
http://snugug.github.io/designing-the-modern-web/#/