Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: not2easy
So what do people consider yesterday's news when it comes to general site design/look? Are you tired of seeing fish-eye pictures of people from above? If so, what else?
- Inverted-L shaped frames
I am a little sad to see them go. They do make sense design and bandwidth wise. Why blog my pipe with 'includes' if I can have it local once and for all?!
BUT not so for SEO. I think that was the main reason they disappeared. Robots didn't understand them. And we started to use tables (arghh) instead.
I think css might be next. 'That was soo turn of the century' :)
You know, the little graphics (bubbles, cats, etc) that would follow your cursor around on the page. Interesting for the first 3 seconds. Annoying as hell after that!
First screen is a title and those other informations that you usually find on the title page in a book, including time of publication (1996ish, no updates). No navigation.
You scroll down and find a foreword. Still no navigation.
You scroll down once more and find the beginning of a loooong table of contents, many screens deep. And this table of contents is the navigation.
You click on a link and are sent waaay down the page. No navigation. You either have to scroll or hit the back button.
What's so bad about horizontal rules (<hr>) in and of themselves? I can see avoiding 20 pages of them but otherwise, what's the beef?
I've seen something like the equivalent used in documentation circles. Generally speaking, a horizontal line breaks up a paragraph fairly well, which makes scanning content a little easier especially with bold labels along a left-side column. Is it that some '90s tools can still be used to good effect (like tables, Flash, etc.)?
Also, I'm no expert here but what's the beef against client-side shopping carts ala Actinic etc.? I've never used it before so please enlighten me.
Problem: Selling a design to a mid-small company or individual. Good design goes out the window after the first draft, and you end up posting some piece of schlock because that's what the "shoulda been a used car salesman but became a realtor instead" client wants.
I can think of one person in particular, who makes 7 figures in commission per year selling acreages, who I like to refer to as "Boss Hog" because he's a short, portly, arrogant twerp in a ten gallon hat who's decided he needed "One of them web page thangs."
I designed a beautiful, clean, professional site for him, that he hated. In the end, I coded up a page that contained virtually every "don't" listed here, charged him a couple sets of arms and legs for it, and left him smiling. (Then changed my e-mail addy and got call display so I'd never have to hear from him again).
Good web design = having no opinion, just the ability to do whatever stupid/smart thing your client wants.
Usually with the volume set twice as loud relative to the internet radio I'm listening to. Nothing makes me hit alt-F4 faster.
Note on Tables: Useful when you wish to display a table of information. Properly used they are fine. The multiple nested tables used to control layout where one would have done are the problem.
Properly used they are fine
Glad to find someone who agrees with me on this! For laying out tabular information they are still an option to cosider. But of course if used badly can result in code bloat, etc., and divs are preferable for most layouts.
I find that many people, especially those new to CSS, consider them as old-fashioned and automatically jettison them in favour of divs no matter what is the best solution or the amount of work involved. The result is a lot of posts in the CSS forum asking why the poster's design doesn't work in all browsers, and what hack can get around it.
Just my 2c's worth, which I'm sure a lot of people will disagree with. :)
Properly used they are fine
Glad to find someone who agrees with me on this!
Count me in as a supporter. I love tables, I love nested tables, and properly used they can be great. I prefer working with tables and I prefer how they look. And who's worried about 0.22 K of extra code now? It's 2004 for crying out loud.
What I am tired of seeing are CSS sites. No, really. And I don't like working with CSS. OK, this is not a debate about CSS vs tables but since everyone is listing their pet hate, mine is CSS.
<no flames please :-)>
Disabled right mouse button garbage is easy to get past.
Just press 'ESC' at the same time you right click and 'presto!' the context menu appears.
"Save Picture as..." here I come.
Also, far too many of the right mouse button-disabling scripts don't quite work right in Mozilla, I've noticed. They let the context menu display, and THEN pop up a dialogue box with the menu still usable. Oops.
entire pages that have been made in photoshop, sliced in image ready (or FW) and exported with messy tables, the one central image has been deleted and 10px fixed text pasted in instead. all the other images have been left in place instead of being sliced or marked up properly.
AACCKK! I've seen a few of these things... which immediately caused me to exclaim, "what were they thinking?".
Aside from the difficulty of maintaining such sites, designs like that are horrible resource hogs (how many HTTP requests for all those images?), not to mention horribly inaccessible (alt tags? what alt tags?).
Whattsisname, Flanders, from pages that suck, calls it "mystery meat navigation"
As far as what I REALLY hate though... As soon as I see a java 'applet loading' message at the bottom of my screen, I leave. I don't even wait around to see what the java actually *does*.
Also, I'll add "web sites in front of me that don't use their turn signals"...oh...I'm mixing my pet peeves again...
A) they create a lot of bloated code, your pages end up heavier than they need to be.
B) They become complicated and difficult for a later developper to work on.
C) Unless you're really careful, they can produce stunningly different results on different browsers.
Having said that, I use them all the time because I'm too damn lazy to learn CSS. Also, it creates a page that just baffles code stealers who view source.
I looked at other sites and implemented several of the ideas and tricks in say "Eric Meyer on CSS" to demonstrate that they would work with the web publishing system. Eventually I started taking calls for suggestions on what to do, such as colors, or websites people liked. I even implemented our website inside our webpublishing system updating the designe done by the previous web guy so it validated, at least before I put in all the WebObjects stuff...
One thing that I did was make some gradients in Macromedia's graphic program, Fireworks. I also made a metallic looking site. Almost all of them would be inverted L designs though none used frames.
Eventually we had to design a site to market the web publishing system. It was a major design by committee, I just did the typing. It ended up being blue with several gradiants. Basically it has gradiants everywhere. It does download really fast cause all those images are really small but I immediately thought of this site when reading this thread.
Now-a-days I ownly have my own little hobby site, which you'll be happy to know doesn't seem to have many of these complaints. It does have a dark background, but you can swap it to a light background using a style sheet switcher. ;-)
I still remember the marketing guy and my boss argueing over using red on the current section color in the menu. I suggested orange and that was probably one of my only suggestions in the site. Orange is a new trendy color in web design. I blame Zeldman, Arstechnica also has a lot of orange. Blues and greys are of course popular, but lately I see a lot of orange on the web. I even use it myself. ;-P
Cheers from Japan.