Live data from Hacker News

Make Your Mockup in Markup

24ways.org

1–10 of 18 posts

Re: Make Your Mockup in Markup

#2
When doing work for others, I still think drawing up something in Photoshop is faster.

However when doing work for myself, I don't need to draw a mockup to show myself, I can simply picture what I want in my head. So I've tended to go straight to HTML for my own stuff, and go into Photoshop only to produce some graphical element. This way I also skip the painful part of transferring the pixel perfect photoshop design into rendered HTML/CSS.

Re: Make Your Mockup in Markup

#3
Wow, this is exactly how not to design.

Separating layout and content is a mistake. Content should be inextricably linked to how it is presented. This is what design means; it means taking content and displaying it in an understandable and pleasing way. Every piece of content desires to be presented differently.

This is exactly why CSS is such a horrible pile crap. It trains designers to separate content from presentation, and it's not designed for page layout. CSS is designed for forcing content into little boxes.

As long as people design for the web by separating content from presentation, we're never going to evolve into something better.

Just look at the end result of this article. It's a boring, lifeless "design" as a container for any type of content. It goes completely counter the very soul of Zeldman's quotation.

Re: Make Your Mockup in Markup

#6
I've worked in both PS and HTML for mockups.. in different team workflow enviros, sometimes out of necessity, sometimes as experiments, laziness etc.

Photoshop almost always produces more esthetically pleasing layouts. Its also a lot faster to knock out ideas. And if you have clients (not solo) its the only way to go.

When you work in HTML first its very easy to back yourself into a wall. You're constricted by boxes and CSS, and due to the difficulty making certain things work in CSS you're usually less apt to do something difficult, so you get very dry layouts.

Hacker News is a great example of a site that was designed in HTML haha. One giant column, no chrome, no styling of almost anything. Easy in CSS, hideous on the eyes...

Re: Make Your Mockup in Markup

#7
post #6

I've worked in both PS and HTML for mockups.. in different team workflow enviros, sometimes out of necessity, sometimes as experiments, laziness etc. Photoshop almost always produces more esthetically pleasing layouts. Its also a lot faster to knock out ideas. And if you have clients (not solo) its the only way to go. When you work in HTML first its very easy to back yourself into a wall. You're constricted by boxes…

Hacker News is simple, sure. But "hideous on the eyes"?

Re: Make Your Mockup in Markup

#8
post #7
post #6

I've worked in both PS and HTML for mockups.. in different team workflow enviros, sometimes out of necessity, sometimes as experiments, laziness etc. Photoshop almost always produces more esthetically pleasing layouts. Its also a lot faster to knock out ideas. And if you have clients (not solo) its the only way to go. When you work in HTML first its very easy to back yourself into a wall. You're constricted by boxes…

Hacker News is simple, sure. But "hideous on the eyes"?

I tend to agree that the design of HN isn't all that great. It's simple and usable, but it's not the easiest on the eyes. I've seen simple sites that were also beautiful. The design isn't what really matter on HN, though. The community is what's beautiful, so I can ignore the fairly uninspired design.

Re: Make Your Mockup in Markup

#9
post #3

Wow, this is exactly how not to design. Separating layout and content is a mistake. Content should be inextricably linked to how it is presented. This is what design means; it means taking content and displaying it in an understandable and pleasing way. Every piece of content desires to be presented differently. This is exactly why CSS is such a horrible pile crap. It trains designers to separate content from present…

I can only hope you're joking. Design, by itself, is pointless; content, by itself, is the point.

Re: Make Your Mockup in Markup

#10
post #3

Wow, this is exactly how not to design. Separating layout and content is a mistake. Content should be inextricably linked to how it is presented. This is what design means; it means taking content and displaying it in an understandable and pleasing way. Every piece of content desires to be presented differently. This is exactly why CSS is such a horrible pile crap. It trains designers to separate content from present…

I can only hope you're joking. Design, by itself, is pointless; content, by itself, is the point.

Badly-presented content can be useless or misleading. Good design may not draw attention to itself when you're paying attention to the content, but it's still there. e.g. http://graysuite.blogspot.com/2009/06/consider-my-mind-blown...
Post reply on HN