Slashdot Mirror
What Makes a Good Web Design?
Grand Master Math asks: "I'm currently redesigning my website and I have checked out tons of various web sites, gone from link to link, etc...to find the best web design techniques, layouts, and features. Wow Web Designs proved to be a pretty useful site, as it showcased virtually 'the best of the web' in design and creativity. I was wondering what the Slashdot community has to say about web design and what the best web design should implement and address. From browser compatibility, to simplicity and complexity, and customization to user interaction, what should a perfect web design incorporate?"
Too often, people get too gadgety when they design software. Keep it as simple and as direct as the functionality and purpose of the site allows you to. Gimmicks are worthless. The best web designs get out of the way and promote the presentation of their content. Once you've taken into account the structure of your content, half the battle is over.
It seems that web design has changed over the years in order to better accommodate database-driven websites. Text graphics, for example, are pretty much out.
Check out the big boys and see what they've been doing with their sites in order to compensate for massive quantities of content.
I'm biased, but I've got to say that the LDS Church website has done a remarkable job of integrating content and design in an attractive and useful way.
Got Rhinos?
Whats more important?
The "look" of the website, or the "content"?
Glammer up garbage, and its still garbage. Glammer up content and you've got a blockbuster site.
Just a tidbit to think about when redesigning.
BTW - Cliff, you realize that this is a "need hits on my website" article dressed in "AskSlashdot" clothes, right?
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
Good web design is like good music or good writing. It's only good insofar as it meets the desires and expectations of the audience. My wife and I think Son Seals and Koko Taylor are The S**t. The 18 year old young women in our WSD are bored with them. They like (boring, rhytmless, tuneless :-) techno.
Some people LIKE lots of Flash, animated buttons and dancing bologna on the screen. I like clean and simple. Each is appropriate for different tasks.
The question is, as always, "What problem are you trying to solve?"
The man who never alters his opinion is like the stagnant water and breeds Reptiles of the Mind -- William Blake
Don't EVER put music or other noise on your web page that plays without user interaction. There is nothing wrong with a button that says "play" but if you make noise happen as soon as the page loads then your page sucks and I don't care how pretty or useful it is otherwise, I will close it immediately and never load it again.
The problem is, just which page is making the noise?
You really can't go wrong if your website follows those three principles. There are hardware concerns, too (make sure your servers and your connection is up to the expected task).
Light a fire for a man and he'll be warm for a day. Light a man on fire and he'll be warm for the rest of his life.
1. World Wide Web Consortium is thy God. Thou shalt have no other gods.
2. Flash is evil, and of the devil. Flash is blaspemy.
3. Javascript can be useful for on-page functions that don't necessarily require a server call, but remember your page still still fundamentally work with no javascript enabled.
4. Images should be used for illustrative purposes, not to show you found a neat image and *never* as a background.
5. Images should be small and reduced to webpage resolutions.
6. Content shouldn't be laborous to read. Black on white text is the best, but at least always make sure to use contrasting colors.
7. Style sheets should always be used (see number 1) but make sure that necessary style pairings (such as colored tables and the text within) are defined in the same scope. A page-declared table color and text/css file declared table text color could cause problems if your style sheet file doesn't load.
8. Design for non-compliant brower protocols *only* if your business depends on it. Private sites should *always* be written to the HTML specs (see #1) all browsers be damned.
9. Do not covet they neighbors hyperlinks. Links should be used in *context* and not in a random listing. Don't say "you can find a link about greyhound adoption *here*." Instead, write either "There is a lot of information about *greyhound adoption*" or "*Greyhound Puppies Inc* has a lot of information about greyhound adoption." All of this results in a page more useable by non-traditional browsers. (see number 1)
10. If you change the color of links, you should make sure that the default colors (blue, purple, red) will show up on your site. Another reason not to use picture backgrounds. Also, don't ever *ever* reverse the color scheme... cool (blue-like) colors for unvisited links, purple or red-like (hot) colors for visited links.
Frankly, I think you're asking the wrong crowd.
Of all computer users, the Linux crowd is the least qualified to comment about design. Oh sure, there are exceptions, both among Linux users and among Slashdot readers, but just read the comments that have already been posted. The common thread is that people wouldn't want to sacrifice content for a flashy web site, and that just shows their ignorance. These people don't realize that good design does not involve compromizes. Good design is about presenting the content in such a manner that the appearance enhances the content presentation, not distracts from it.
Besides, look at the state of 99% of Linux software, especially the open source stuff. User interfaces are the last concern of the developers. It's obvious to me that the majority of Linux developers and users really don't care, or just don't know anything about, good design. But, I guess I should cut them some slack, since it's very hard to be a good programmer and a good designer. Yet I'm disappointed that most developers don't try to get good design ideas from others.
So yes, Virginia, you can have your cake and eat it too, provided that the web site is designed by a real graphic designer. Such an individual has both training and experience in creating designs that work.
And the men who hold high places must be the ones who start
To mold a new reality... closer to the heart
Especially since you NEVER need to use frames
I dispute that: there's a certain very well-defined set of circumstances in which using a frameset is beneficial. Although I agree that 99% of the frameset usage on the web is inappropriate, in certain circumstances framesets can be used for efficient navigation and still look good - the main advantage of frames is that they only need loading once - it's a frivolous waste of bandwidth to put the same graphical navigation bar on each page, for example (not that I'm a huge fan of graphical navbars).
Still, the rule for frames is: If in doubt, don't use them.
Actually Eric Binna and Lou Montoulli invented the Blink tag at Netscape. It was an easter egg, it was never documented by Netscape, they just used it a couple of times on their Web site. It was actually meant as a joke.
To answer the original question, Web designers should be taught to use as little active code as is necessary. I am fed up with sites that collapse in a mess of poorly debugged Javascript. At least these days Javascript rarely causes the browser to crash, but you can still go to a major site and hit a Jscript bug with a major browser release.
The main design point I think Web Designers need to be taught is allowing the user to decide how to view the site. I really get fed up with sites where the main purpose is to satisfy the Web Designer's ego.
My absolute hate is sites that start to mess arround with the controls on my browser. Especially those that try to disable the back button or fix the window size. At home I have a large LCD display, only i spend a lot of time looking at sites that insist on folding themselves up to a postage stamp size in one corner with 6pt fonts.
Don't ever put 'best viewed in 640x480 on your site, or anything like it. The whole design of HTML was to make that type of thing unnecessary.
IE now allows you to enable javascript on a per site basis. since turning off Jscript by default and only enabling it when necessary the quality of my browsing has improved greatly. A major side benefit is that popup ads no longer work. Now if we can only persuade MSFT to allow Macromedia to be disabled on a site by site basis or provide a button that says 'Never download this application it is a crappy piece of crap whose sole purpose is to bombard me with crappy adverts i don't want to see'.
Looking for an Information Security student project suggestion?
Try http://dotcrimeManifesto.com/
The difference is that you can make links open in a new windows by control-clicking (or whatever) on them. But if the developer forces all links to open in a new window, how do I (who doesn't want a new window) make it not open in a new window? I can't -- the developer has overridden that option.
To provide the user with choice (which is one of the most important things that a website developer can do), it's important to not force particular UI styles on users. Give them choices. In this case, the only way to do that is by not opening links in a new window.
-Waldo Jaquith
I do web programming for a living, and we get into some very interesting conversations when we're designing a site. Occasionally, I get some very wierd requests for new and novel interfaces. This is a bad idea.
Although the web is fairly new. almost everybody is expecting to see a few things.
- A navigation bar on the left
- A breadcrumb, like on Yahoo!
- Navigation at the very top
You do anything different, and you risk confusing the hell out of your users.You can argue all you want about why your interface is better,but unless you can hard data from usability testing, don't break tradition without a very good reason.I may be heavily biased, since that is what I do all day, but make absolutely sure your code is valid HTML, and leave out all the kruft. Pretty much all WYSIWYG design interfaces by default don't put out valid html, so don't use them. [Emacs |VI] will perform admirably, produce clean code, and if you use a server side scripting language and hide most of your code in templates, will be as fast or faster than Dreamweaver or Frontpage. (You are using PHP/Coldfusion/CGI/ASP, Right?)
For the Love of (insert your choice of deity here), don't make a site all flash unless you have an extremely good reason to. As of yet, I have never heard of a good reason to do so, but they might, in theory, exist. Anything that you put into a web page, be it Javascript, Flash, Shockwave, audio, video, and massive, massive graphics, slows down the site, makes it harder to load, and will turn people away. I'm not saying to use NO graphics. I use quite a few at work, but keep them small, and realise that users very well may have images, stylesheets, or browser-supplied fonts turned off.
Finally, remember what HTML is designed to do. HTML is a markup language designed to format text. All the nifty graphics and such are good, and they have their place, but they weren't invisioned when HTML was designed, and in a sense, they are foriegn to the medium. Use them with caution.
Whoever mentioned the book Don't Make Me Think has a very good point. That one sentence tells you more about User Interfaces than many books ever will.
Listen to the clever people. Not me, but Joel Spolsky.
From his book, User Interface Design for Programmers:
Usability is not everything. If usability engineers designed a nightclub, it would be clean, quiet, brightly lit, with lots of places to sit down, plenty of bartenders, menus written in 18-point sans-serif, and easy-to-find bathrooms. But nobody would be there. They would all be down the street at Coyote Ugly pouring beer on each other.
(he also said that on his site in Nov 2000.)
Joel's a far more clever guy than I, and is always much more eloquent in expressing ideas. You should listen to him, too.
J.J.