Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Graphics Software

Interview: Lynda Weinman 115

Andy King writes: "We interview the design diva herself, Lynda Weinman. This wide-ranging talk sheds light on Lynda's work and teaching, her humble beginnings, and where she thinks Web design is headed." Mostly good, sensible advice -- though not incontrovertable. (Not everyone believes in using tables to control the layout of text, for instance.) Weinman's advice is down-to-earth, and worth reading for anyone who wants to make Web sites functional and aesthetically pleasing.
This discussion has been archived. No new comments can be posted.

Interview: Lynda Weinman

Comments Filter:
  • by Anonymous Coward
    Presumably because she cares about typography, and there's no way in hell that a markup language is going to give you the control of appearance that you need to do anything interesting with design.
  • by Anonymous Coward
    all the bad web designers I've ever met are the product of books and bad teachers. The best web designers from personal experience the last four years are all self taught and never read a single book. With that in mind, I've look at few of her books. the content is there, but there is no substitute for careful observation and self-motivation. the key to good web design is more about keeping an open mind than reading a book.
  • You guessed right. See the w3c [w3c.org] for all your HTML specification needs. Personally, it's the only place I go for answers on HTML questions. If it's not in the spec, it's not worth my time.

    The current version is HTML 4.01 [w3.org]
    Or you can glance at the previous version, HTML 4.0 [w3.org]
  • I've known people who were self-taught from books who have very good design skills. Granted, if you take Laura Lemay or Lynda Weimann as the web design gospel, you'll get in trouble. On the other hand, I started out with the NCSA tutorial, picked up some of the better things in some of the books available, and adjusted my style such that my site were easier to view and use.

    I admit to being a format freak, but that's self-taught. I know other people who are the same way. Bottom line--just because someone learned HTML from a book doesn't mean that their sites will suck. My web design philosophy can be found on my "Please hire a graduating college student" page at my thoughts page [exhibit-a.org] on the site.


    Who am I?
    Why am here?
    Where is the chocolate?
  • Actually, I still think the "magic 'O' word" in this case is "Open standards", but the other two 'words' are required to ensure that.

    However, Open Source goes a long way to helping out the other three goals: if you can simply recompile, or patch the source, what could be more open and friendly than that? It's additional and optional, and programmer-friendly. No one else should care, except that they might get an enhanced product out of the deal. But we'll see how Netscape 6 is soon enough...

    But I was just sharing a quote I found interesting, that raised my opinion of Lynda, who I had never heard of before. And as no one else commented on it before me, could someone kindly explain how I'm "Redundant" too?

    I also thought the guy posting to explain that this wasn't a "Slashdot Interview" candidate was being very helpful, and I think he got moderated down for his troubles. Do I not get moderator access because they know I won't moderate down the good posts? No, really, I'd like a reply, preferably from the people who moderate down on this thread. :)
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • Wow. My nemesis, thy name is gargle.

    Even if a post doesn't contribute to the discussion, *or* if you don't like it, it isn't redundant unless it's been said. And in this case, it seriously wasn't offtopic, since people were *still* posting interview questions! I would moderate it as "Informative".

    A warning like that needs to be at the top, so people don't waste their time writing questions that won't be answered, and seriously don't waste their time flaming other people who write the questions...

    I know how people get mod points, but I have yet to see the logic in the system. I've been reading slashdot a lot less lately, but I'm sure I'm not an average user, or whatever they're looking for.

    From what I've read thus far, I like Lynda because she seems to understand the realities of the situation while still hoping for a real solution.

    You must realize that web sites would be much more usable and aesthetically pleasing if they worked the same way, on all web browsers? Like maybe if I didn't have to see unsupported character codes in HTML that only work in Windows/IE5 for some reason? Hmm? I wonder why that happens...

    And for the record, I didn't say a damn thing about "Open Source", she did, and you did. I liked the quote, and was surprised I found it there, amid all the web newbie tool talk, and thought the Slashdot community might find it interesting. I also mentioned the other web design points I was interested in from the article, which you chose to ignore.
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • Hmm. I browsed that page in lynx, and didn't have a problem figuring it out. The left frame was "menu", since lynx supports frames. (and it should, since frames finally made it into the spec--are there any major browsers that don't support frames anymore?)

    I would have preferred tables because I still think frames are evil, but okay. (On Lynda's main page, she's got a kewl script that breaks out of frames. ;)

    I know why people use graphics that are simply text. If there were a good, standard way to give everyone the same fonts, we could just use that. But there isn't, not really.

    Lynx also shows the names of the images in the links, and these images are all named consistently. The ALT text would be exactly the same, except without the ".gif". w3m goes one better, and just shows the names, and that they are images.

    Sure, these are technically errors, but please explain to me who would run into them? Someone using Mosaic with image loading turned off? Please. It isn't great, sure, but it isn't a "monstrosity".

    However, you're right, someone doesn't know how to write HTML, was in a hurry, or hacked a pre-existing page. You should never have a closing body without a starting body tag, and frames don't need a starting body tag, so...

    But even with all that, these pages look fine in most any browser, AFAICT. Isn't that the point?
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • I am probably wasting my time on yet another ignorant "web designer", but here goes..

    HTML is designed to be universally accessible. That means the information can be accessed on your fancy PC, a PDA, or by a blind person using a braille terminal. What you are asking for is to piss on those that don't have the necessary hardware to render your "design" or even worse they _can't_ because of their disability.

    I know, "I am not targetting blind people. They are not interested in what I am doing." yada yada. I am sure if you, or your children, lose your eye sight then you will lose all interest in your previous life too (or if you are blind you don't deserve a life at all or at the least you should be sent somewhere where you can't bother us real people). Umm, yeah, that seems likely.

    The "funny" thing is that the people that had the most to gain from WWW (all those who couldn't read the newspaper because it wasn't available in Braille or on tape) are constantly being screwed over by the likes of YOU. Yes, lets use PDF all of us so that we can really shut them out.

    Once again. You people make me sick.

    /mill
  • Maybe. Maybe you are right. Or it could be that I am just disgusted by the ignorance shown by "web designers".

    Just because because you can park in the handicap space doesn't mean you should. Just because you can screw those that had the most to gain from WWW over doesn't mean you should. Even if it means you have a shorter walk to the mall or a way to copy the paper media - verbatim.

    If my web page doesn't please your eyes you can always use your own client side style sheet. One can't make up for abuse of HTML by "web designers" though.

    Funny thing is the uproar that occurs here each time Linux users are shut out from something and then in the next moment they are perfectly content with screwing blind users (or whoever) over. I, as a Debian Linux user, can at any time go to the store and get Win* instead. A blind person can't buy a new pair of eyes.

    /mill
  • IMO, nothing wrong with Perl/CGI, if the server can handle it. Frames and the like will go away as CSS gets support (ie, Mozilla - as she puts it, open standard, open source, cross-platform). Although, big companies have a history of not 'getting it' very fast - I say 2005 they realize you need more than a graphic designer or a programmer, you need someone who's both, and about 2010 before they actually get something worthwhile. Of course, those are based on rough estimates of technology acceptance, from what I can estimate in my head. It'll probably take much longer :)

  • I run my own web design company, I wouldn't hire her based on what I see of her work on Linda.com [linda.com]. The colors are garish and the text is hard to read against the backdrop. On top of all that, when you click on a link (tips), the left navigation bar goes away. Rule #1 of web design is consistency.

    She is no expert. I would like to see an interview with the folks at WebPagesThatSuck.com [webpagesthatsuck.com]. At least they are up front about what works and doesn't, and they tell you.
  • And did you notice that "webreference.com" isn't mentioned in the Slashdot article and that Andy King [webreference.com] doesn't lead to "Andrew King, Managing Editor (aking@internet.com)", it only leads to the WebReference mainpage, and he didn't start the story by saying,"We here at WebReference [webreference.com] interview the design diva herself, Lynda Weinman. [webreference.com]", he just says we. timothy should have caught and fixed that.

  • I want my column to be 40 em wide not 50% browser width or 150 pixels.


    You ain't never heard of the BR tag?

    That wouldn't work, unless you were using a monospace font. Pre-wrapping non-monospace text is a horrendously bad idea, because you end up with an extremely ragged right margin.

    My opinion: don't try to force it to be narrower. If users really find it hard to read the long lines of text, they can resize their browser window.

    If you
    try and
    force it
    you'll
    just tick
    people
    off when
    they have
    to read
    text
    that's
    all
    squished
    against
    the left
    side of
    their
    browser
    window
    like this.
  • SUV-driving and earth-loving are not compatible.

    I think meat contains some chemicals which support one's sense of humor, because you certainly have lost some of yours... Unless you've never actually had it. :)

    --

  • I am also a follower of the "semantic HTML" religion. However, when you say, "For slashdot to give this woman credence as an "expert" is truly shameful.", you must be forgetting what the default Slashdot page looks like in the first place. Sure, at least /. doesn't use a fixed width column for the main content. But the pages are so bloated (and poorly designed, sorry Rob/Jeff), that I've been using /. in "light mode" for about a year now.

    If the article posted was critical of Weinman's advice, then there would be something to say. As I see it, the comment is entirely consistent with /.'s design philosophy.

  • /rant mode/
    Maybe she's an expert, but has anyone running Linux actually visited Lynda.com [lynda.com]? Can you read anything on this page without a loupe?
    This is another case of One-Os-Design. Sorry, but I can't take advice from someone who obviously doesn't care about cross-platform compability. Not everyone is running MS Windos, you know...
    /rant mode/

    tom

  • Colour choice: go for contrast any time. I prefer dark backgrounds with light text, too, and find (for example) standard M$loth-produced black-on-bright-white painful to think about.

    You've made the right decision, but for some reason, it seems most "designers" do not seem to want to do this. We went over this issue in my User Interface grad course, dark backgrounds with light text are better for the human eye(it's been proven), but people want to imitate paper for some reason !!!

    BTW - Good advice in all the other areas.
  • SUV-driving and earth-loving are not compatible. Maybe electric car-driving and earth-loving.....

    And vegetarian's snobs? Hah!!!!!!! I've been one for eight years and am treated like a freak/misguided fool constantly by flesh-eaters. It gets very old.
  • Her site is not bad, and I might bookmark the "safe web colours" table, but it's not really a lot to write home about, and she touts her course and books everywhere. This is graphic design she's into, which has very little to do with the web (for that, read Nielson [useit.com].)

    Not so much Diva as Prima Donna, perhaps?

  • (( Colour choice: go for contrast any time. I prefer dark backgrounds with light text, too, and find (for example) standard M$loth-produced black-on-bright-white painful to think about. ))

    Yes, black on white is painful, but it is better than the blue on black I see all too often. The amount of pages with crazy backgrounds I see never fails to amaze. Another tip for those people: teal text on a gray background with a dark image is fine until the image disappears or fails to load. Then I kiss the illegible page goodbye. personally, the user has the power to change the colour to what he/she wants in options. But, at your suggestion, I changed my page (by swapping 2 things in one .css file) and everything is different. I expect everbody to access my pages with either a gui browser or with lynx. either way, it's white on black.

    I open new windows when a user clicks on an outside link. But only one. I use the Target property to open to "_", which replaces content in that one window instead of one each.

    I'm not a big fan of multiple images, as I prefer to do things with type. Sometimes I wished you could build all your "fancier" (layers and the like) text within the css borders, never to render in plaintext (or to render differently).

  • Lynda: I have never created a Web site other than our own.

    Who needs real-world experience when you can just sit on the sidelines and pontificate?

    The design of lynda.com is, umm, not the worst web design I've ever seen, but it certainly isn't the best. Some of the color schemes are questionable, but no worry -- just go to another page on the site and you're sure to be treated to another color scheme entirely. Consistency is every bit as boring as all those rectangular objects that plague the web. And the site looks pretty bad in Lynx. And I can't help but raise my eyebrow at anyone who consistently capitalizes the word "Web" in the year 2000.

    Oh, and thanks to whoever pointed out the poll on lynda.com about "what resolution do you design web pages for?" I can only shake my head and sigh...

  • Frames have always been, and will continue to be the worst design, breaking the back button, bookmarks, and just about anything else that the web was built on. Side note: I had never heard of this lady, till she was interviewed on digital village [digitalvillage.org], and sadly I missed the interview. I immediately visited the site beforehand, and thought it was light on content.
  • Who cares? Can you read it? Then its good enough.

    Damn, I bet you are the designated driver at parties too...


  • Hmmm, yeah. There are several considerations in the choice of colour.
    I'm typing this in netscrapie on linux though and this text box is black on white, the rest of the page being grey. And this box is awful to look at.

    One approach I've been playing with (and it's all too obvious from my page :) is to take a multi-coloured backdrop and remove one colour, e.g. green, from it, and then use that as a main text colour for those bits where the font is small enough to get 'lost' in the backdrop. Then you stand back a couple of feet and if you can't read it, try again :)

    As for opening new windows - please don't! I have a very serviceable middle button that does it for me, or I can right-click+"open in new window"; if I get the impression that some pages will screw up my left-click, I'll be very unhappy... ;|
    ~Tim
    --
    .|` Clouds cross the black moonlight,
  • Take a look at this [w3.org], and then compare it to this [w3.org] (the guy he is responding to). Yes, his voice is absolutely worth listening to. Correctness before prettiness, that's just my two cents...

    And btw, some of the quotes are excellent.

  • Lynda,

    I don't know if you will get to read this posting or not (I cant imagine it making the cut of questions presented to you, and I dont know if you read Slashdot regularly) but I just want to say that I think you are right on with your view of how websites should be designed. A couple years ago I bought a copy of "creative web design" and I've worn that book down considerably.

    I already had a pretty decent knowlege of HTML prior to reading it though I both enjoyed reading it and learned quite a bit about topics the average web developer pays no attention to such as:

    • font selection (appropriate use of serifed and sans-serifed fonts)
    • color selection (browser-safe colors!)
    • proper selection of graphics formats (gif vs jpg... that both are approporiate) [sorry, RMS!]

    It was also a great tutorial on javascript and photoshop (after learning the concepts of using photoshop to design nicer graphics from this book I was able to take what I learned and use the GIMP ;)

    If more web designers read this book, we'd have a much nicer web. I wish you (and your brother the Javascript man) the best of luck, and thank you so much for the excellent material you've provided us with!!

    Bill

  • I hate to say this, but I think Lynda is overhyped. Yes, her books are good, I own one myself ($5.99 in the bargain bin at London Drugs!) but as a woman, I can't get over her snotty, holier than thou tone. I think she's a skilled person who kind of let her popularity in the way....that and some parts of her website haven't been updated in ages. Just MHO. Perhaps it's something that comes out in print.
  • That's interesting, you could say the same about today's writers. A lot of them are not writing from personal experience, but are rather taught by writers who think they know what writing is.


    I found Preparing Web Graphics useful, that's the book I have, especially the colour charts.


    I guess what I also tried to say in my earlier post is that she has an incredible following, like Martha Stewart. I can imagine all these wannabes - and the sort of idea that sounds like "Be like me, buy my book" or "Buy this book and be elevated to web god/dess"


    Shrug :-) I'm happy with my designs - utilitarian on my book site, and very graphic on my horse one.

  • *g* this is exactly what I mean in my earlier posts about Lynda being like Martha Stewart :-) a good teacher can teach, but a good student must also be able to learn and explore on his own. If you think Lynda is the be all and end all of web design...*shakes head*
  • OTOH, design people should know HTML. I've seen some pretty sites that could benefit from HTML - you know, the people who think mapping a 50KB image is no big deal. (cut it up!)


    *g* ugly pages - isn't that 99% of Geocities?


    I suppose another thing that irks me is that when people who call themselves "artists" or "designers" make some god awful background img that everyone and their dog uses, and throws readability out the window.


    I think there is so much one needs to know to build on the web. FrontPage won't make you a brilliant HTML author either. To design properly, you must know how HTML actually works, and work with the limitations of the code. Using tables for design is a pretty big hack in itself, IMHO.

  • There isn't any wysiwyg editor on the market that produces ready to publish html

    Actually, I watched Lynda's video for Adobe Go Live the other day (my man brought it home from work) and during the few glimpses she gave of the code you could see (and I have confirmed this in person) the HTML it writes IS fairly clean and ready to go. Imagine my shock.

    I write all my sites with Notepad, and even though AGL does some awesome things with mouseovers and image maps, I still prefer to have ABSOLUTE POWER over my code. :-)

    The Divine Creatrix in a Mortal Shell that stays Crunchy in Milk
  • I'm interested in replies from anybody who has visited
    mill's web page [sn.umu.se] and thinks that his is a voice worth listening to on the subject of creating web pages.

    I'm willing to say he is. Okay, the colour choices are pretty hideous, but take a look at the page in your fancy-schmancy browser with stylesheets turned on. Now look at it in your fancy-schmancy browser with stylesheets turned off. Now look at it in Lynx. Now look at the source.

    Those floating yellow boxes with quotes in them are just <blockquote> elements. No layout is done on a per-quote basis. Compare that to trying to acheive the same thing with tables.

    In short, this page rules, and has really made me rethink the viability of doing all of your page layout with CSS.


    --
    The scalloped tatters of the King in Yellow must cover
    Yhtill forever. (R. W. Chambers, the King in Yellow)
  • Offtopic, but interesting.... Where does one find the exact standard? w3c.org, I'd bet... If I'm way off please post its location.

    I wasn't aware an image's ALT tag was required to be html4 compliant...

  • "What's the most hideous use of bandwith-busting graphics that you've seen, and how do we avoid the brainless design decisions that lead us down such evil paths? :) "

    How to prevent it? Easy. Force every web designer to view their work... with a 56k dialup. If you can hold your breath untill the page loads, you got it right. That last part I heard someplace else, but can't remember where. It's 1:30am now and all this Natty Boh is going to my head. :)

  • One of the features most requested by web designers for Mozilla is true alpha channel support in PNGs. I personally was looking forward to this feature. Do you have any comments (possibly compelling reasons) now that mozilla has pretty much decided that won't [mozilla.org] make it in the final release?
  • Re: Perl is not the problem...

    The problem with -most- perl/cgi heavy sites is when they are poorly designed - eg perl scripts all over the cgi-bin directory and lots of heavy ? get strings... If you use mod_rewrite, php or something similar it is possible to make a more friendly site by having url directories for navigation instead of cryptic get commands. Point is, the interaction with the cgi layer -is- part of the UI.

  • From the interview:
    If you don't find the Web site, surely you will bump into a book relating to Web design by Lynda Weinman. It's not that Lynda is everywhere --she is just everywhere that Web developers want to go.
    As a matter of fact, I have never heard of her.

    Does that mean I'm not a web developer?

    Or does that mean someone is fabricating (using a ~random number generator) some hype?

  • Well there's one or two. She has done some valuable stuff (ie working out the 216-colour websafe palette) but these days, she seems (like Molly Holzschlag IMHO) to be more interested in promoting her books/courses.

    If you actually look at her books, the newer revisions dont actually add that much new information. And once you know how to defringe, which image format is better for which kind of graphic, and how to use the 216-color palette then you don't need to purchase four different (~45 UKP) books to get the information. In fact if you read her column in Web Techniques (probably archived) then thats probably all you need to know.

    But she pushes the books, and the courses, and the videos, and the DVD's. And meanwhile, sahe sticks with slightly older ways of doing things, in a kinda David Siegel stylee. Ookay, CSS isn't guaranteed cross-platform / cross-browser so its forgivable, but its slightly old-fashioned. And there isn't a lot of new graphics-oriented generic information; its devolved into books on specific software packages.

    If you're interested, browse her books in Borders or summat, but don't buy. Too damned 'spensive. Get the O'Reilly book on web graphics, or read webdeveloper.com.

  • I wasn't aware an image's ALT tag was required to be html4 compliant...

    There is actually a very good reason for this. HTML is designed to degrade gracefully. Using the alt tag allows for image based designs to degrade gracefully in non-graphic browsers (and in graphic browsers with image loading off.) Think of your typical graphical button. Now think of it in a text browser. Say the image is your logo, or a cute little button that says Home or whatever - and pressing it goes back to your main page. Without the alt tag that functionality is completely lost to someone using lynx or arachne. Set alt="home" and all is now well - in a text browser I still get a control there, with the text "home" on it to let me know what it is. If you have a picture of you on your page, you can use something like alt="a picture of the author (png-50k)" - admittedly this is of limited help to someone in a text browser, but it is likely to be greatly appreciated by people using graphical browsers with image autoloading off, as it gives them the information they need to decide whether or not they want to load that image.

    Of course, there are (way too many) images out there on webpages that don't have any real function at all - in those cases alt="" is appropriate, and the validators have no problem with that.

    What is not appropriate, and very annoying is alt="ALT" which I've seen all over the web.

  • The worst of all are the sites that set the background tho white without setting a foreground, forcing me to leave my web defaults black on grey when I use Windows as white on blue. I wish I could have a browser that ignores the setting in that case.

    Using one right now. Opera. [opera.com] I have it set to white text on blue background, which I prefer. When I hit a page that sets one colour but not the other (ick) or worse yet one that sets both and makes the page totally unreadable, there's a button to disable document settings. Works great on slashdot (text is set to black, background isn't set - if my background was set to black it would be totally unreadable without override, as it is it's just not pretty ;^)

    The linux port is coming right along - I can't wait. I love linux but I find myself rebooting to use the web - once you've used opera netscape just is not acceptable anymore.



  • Lynda: Open standards, open source, browser compatibility and cross-platform compatibility. A tall order indeed.

    If she wants open standards, why is she teaching people to disregard them? If she want's compatibility, why does she teach people to write poor html and deliberately break the cross-platform compatibility that's already there?

    Supporting standards and not designing pages which are browser specific is the real way to keep the market for browsers open and to keep browser technology improving. [anybrowser.org]

    She speaks as if things like open standards and cross platform compatibility don't exist. You seem to have bought this, and think she must be great because she wants them to. This is just bull. These things do exist - they just aren't idiot proof. Just because it is possible to write poor html, violate standards, and by doing so break compatibility doesn't mean they don't exist - it means you should learn to write proper html. Too bad Lynda declines to teach people to do this.

  • If you want more control over display than a language like HTML can provide, the solution is to find another media - pdf for instance - NOT to mangle html.

    What adds insult to injury is her going on to blithely claim to be in favour of standards and interoperability, when she's teaching people to mangle and destroy those very things.

  • However, when you say, "For slashdot to give this woman credence as an "expert" is truly shameful.", you must be forgetting what the default Slashdot page looks like in the first place.

    It's true that slashdot isn't a great html example. But there is light mode (it's why I made an account in fact, now I don't have to keep typing it in, I just set it in preferences and be done) as you mention, slashdot is dynamically generated and that always makes it harder (though not impossible) to produce good html, and finally, even at it's worst, slashdot is far better than her site.

    I don't follow a "semantic html religion" - I am talking about usability and portability, not the results of a validator. Mind you, I'm not saying pages shouldn't validate either, ideally they should, but I'd rather see a purely technical error on a good page than a bad page that validates. Validators will fail a page for errors that are pretty inconsequential, and pass pages that have major problems. I posted an example of the major problems on her site in this [slashdot.org] post btw - these are not picky validation errors, but major design flaws that would be easy to correct if she really cared about "open standards" and particularly "cross-platform compatibility" as she claimed in the interview.

  • ...are there any major browsers that don't support frames anymore?

    I believe webtv doesn't (I've never used it) I am not sure about arachne, and hell one of the many reasons I like Opera is that you can (and I have) turned frames off. People still using older browsers (and there are quite a few, for various reasons) won't have frame support. Voice browsers cannot do anything useful with frames either. And I am not sure palm browsers and the like support frames either, but even if they do, the page is not likely to be readable on that small a display. However if the noframes tag were filled in properly and the alt attributes set not only would all those platforms be able to render the content appropriately - any properly written browser on any platform - including ones no one has even imagined yet, could be guaranteed to handle it properly.

    Arguments that there is no need to use proper html because everyone is using one of the browsers you are familiar with it, and it isn't a problem in any of them, are firstly wrong (practically every browser you have ever heard of, and dozens more that you haven't, are still in use by somebody somewhere) but beyond that they totally miss the point. The whole idea of html is platform independence, and platform independence doesn't mean "this will work on all the common systems you might think of" it means it will work on systems that you have never imagined too. This is the beauty and the promise of HTML, and it is quite possible to fulfill, in the vast majority of cases, with very little effort. There is no good excuse not to do this, particularly when your business is web design!

    ... she's got a kewl script that breaks out of frames. ;)

    I saw that too, and I don't think it's a very good idea to autoexecute that like she does. What if I want to view that page inside a frame? Why not let the user decide whether or not to activate the script? I've seen other pages do this, it's not difficult at all. As it is, if I want to view her page inside a frame I have to turn off scripting.

    I know why people use graphics that are simply text. If there were a good, standard way to give everyone the same fonts, we could just use that. But there isn't, not really.

    You are right that there isn't any way to make an html page show up in the same font on everyones display. This is not a problem with html - it is an implication of being cross-platform! HTML frees the author from worrying about tedious layout questions so s/he can focus on content, while the layout is handled on the browser end. There is no other way to handle this without discarding the entire notion of cross platform portability. A font which looks good on one machine with one browser and one configuration file may be unreadable on the same browser on the same machine with a different config! Let alone the same browser on a different machine, or a different browser on a different machine. Remember - some browsers run in environments that don't even have fonts.

    The whole point to HTML is to free the web designer from having to worry about this stuff. Don't use font tags - label your content properly and let the browser decide on the fonts. The browser is in a position to know what display properties your viewer has - the web designer is not.

    Now that said, there are a lot of people out there that still want to do silly things like using gifs of text - and the standard is flexible enough to allow that, and host of other things, script languages, frames, fonts and colours etc - that are not always portable across platforms. Writing good HTML does NOT mean writing for the lowest common denominator as sometimes is asserted by those who don't want to bother writing good html - it is perfectly possible to write a fancy-schmancy page that is customised for a particular browser on a particular OS with a particular resolution that will still work on any other platform too - this is the genius of the HTML spec. The key is the concept of graceful degradation. When you use frames - use the noframes tag (and don't leave it empty.) When you use graphics - use the alt attribute. These things aren't that difficult - and take far less time than is typically spent tuning pages for even a single display.

    Lynx also shows the names of the images in the links, and these images are all named consistently. The ALT text would be exactly the same, except without the ".gif". w3m goes one better, and just shows the names, and that they are images.

    Ok, there are two browsers that are going out of their way to compensate for the poor design of the site. BTW, I just checked it out in lynx myself, and while it is sort of usable in lynx, this is because lynx is going far beyond the call of duty in trying to handle these situations by displaying the filename in absence of an alt tag - you cannot assume any other browser is going to do this. A good web designer does not assume that the viewer is using a browser that s/he is familiar with!

    Load that page up Opera with autoload=no show=yes (mode 2) and all you get is two frames, the left one is nothing but white space, the right is white space down to the bottom of the page, then two links, both with the same text, "Learning Photoshop 5.5 and ImageReady 2.0 for the web." I haven't bothered to reboot to check this in Netscape, but Opera in mode 2 generally renders almost identically to Netscape with images turned off. Put Opera in mode 1 (load=no and show=no - text only mode) and you now get a bunch of undifferentiated image-boxes in both frames, most (but not all) of which are links, each box marked with the same word - IMAGE. Opera *will* render the page just fine - if you put it in mode 3 and enable frames, but the fact that the page fails to render meaningfully in 2 out of 3 modes (and in any mode without turning frames on) is damning. By comparison Slashdot (hardly a paragon of good HTML) renders in a usable fashion in any configuration.

    Your guess is as good as mine precisely what that page would sound like through a voice browser - but I do know that if the alt attributes were set and the noframes tag was used properly a voice browser would be able to handle it properly, and that as it is a voice browser is simply not going to be able to handle it in any meaningful way.

    However, you're right, someone doesn't know how to write HTML, was in a hurry, or hacked a pre-existing page. You should never have a closing body without a starting body tag, and frames don't need a starting body tag, so...

    Yes, and while this sort of thing is unfortunately rampant on the web lately, the fact that she sets herself up as a teacher of web designs makes it particularly shameful.

    But even with all that, these pages look fine in most any browser, AFAICT. Isn't that the point?

    I hope I have made it clear that this page will not in fact renderly properly in any browser, and that is my point.

  • Actually it looks ok on Opera - IF you mess with the window size and/or zoom function for awhile. I totally agree with you though, the design is awful, and her advice is awful. I'm really ashamed to be a slashdotter today... ugh, she's being held up as an expert, a teacher, a role model... this is sick.

  • That's fine. I have nothing against artful designs, or even WYSIWYG editors for that matter (they are great time savers.) But neither of those is an excuse for bad HTML, and that's what I found all over her site. There is no excuse for an empty noframes tag. There is no excuse for a page of links, all tied to graphics which are simply obfuscated text, with no alt attributes. Particularly when this page belongs to someone who presents herself as an expert on web page design.

    I am no expert on web design, but I was able to find three serious errors on one of her pages without even trying. Design errors, that flaunt ideals she presented herself as an advocate of in the interview. I am NOT talking about running her pages through a validator and bitching about picky pedantic errors - I am talking usability and accessibility problems. Ones that could have been fixed in a few minutes if she cared.

    Sure, it was probably her wysiwyg editor, but that is no excuse. There isn't any wysiwyg editor on the market that produces ready to publish html - and likely never will be. You use them to rough out your page - then you tidy it up before you publish. Any web design student should know that, let alone a teacher!

  • by Arker ( 91948 )

    Imagine trying to navigate Slashdot without any images...

    I do. It's nice. Want to see slashdot the way I do? Turn off image loading on your browser (if you have Opera use mode 2, this is what I am actually using, but Netscape with image loading disabled will be very similar) and load up http://slashdot.org/?light [slashdot.org]

    Not only does it load a lot faster like this, it's also a hell of a lot easier to read and navigate.

  • I F YOU PAID $1,000,000 to advertise on the Super Bowl and only viewers with a Sony 35 inch TV set could see it, would you be getting your money's worth? [shore.net]

    Accessible web design increases the size of the audience for your page. Inaccessible designs lock part of your audience out. How is that justifed by "da bottom line?"

  • Um, font selection? Isn't it supposed to be up to the end-user, not the developer, to pick what fonts they use for headings, body text, etc.?
  • it isn't redundant unless it's been said
    ...
    A warning like that needs to be at the top


    It has already been said, and a warning is at the top. It's called the article in question.

    From what I've read thus far, I like Lynda because she seems to understand the realities of the situation while still hoping for a real solution.

    As other people have pointed out in the thread, Lynda does not practice what she preaches. Liking her just because she's smart enough to make a populist remark in an interview seems a little too naive, especially given her previous track record (as you point out).
  • The current version is HTML 4.01
    Or you can glance at the previous version, HTML 4.0

    Not quite. The current W3C recommendation is XHTML 1.0 [w3.org], which is very similar.


    Turn on, log in, burn out...
  • See, right here, you're talking about one of the extremes. I didn't say slashdot is all about the little boxes. The little boxes aren't what make slashdot so successful, they just help organize stuff. And sure, you can customize it so the boxes disappear, but then you lose certain information. If that information isn't relevant to you, then ok, get rid of it.

    As for the whole world living off of 2400 baud no graphics terminals, no. The reason the internet has gotten the hype and growth(for better or for worse, that's a whole different discussion) is because of things like the web and its mixture of graphics and text. And like it or not, that's how things are now, and they won't just go back to the past. You personally may like just pages and pages of plain text, but the average person definately does not. I'm not a big fan of flashing animations, or whole page image maps any more than you are.

    Although it's a cliche, a picture can be worth a thousand words. We live in a very visually based society. Most people access their comptuer through a gui interface. Why? Because it's easier, and it's nice, and they like it, why shouldn't the web be the same way?

    And I'll say it again, it's all about the happy medium.

  • by BandSaw ( 104086 )
    It takes no aptitude to make "attractive" web pages. All it takes is using MS-Hype-Vcurrent+1, load it up with cheap clipart, obscure with flash, make sure the fonts don't display right on Netscape, and you're there.

    And yes, I did visit his web page, and the quotes he has chosen show a sharp mind, on par with New Yorker cartoons.

    Now, I understand that some people consider pokemon and a Big Mac to be high art. And I'm not going to diss you for not liking his site.

    I do suggest, however, that the point of his site is content.

    Perhaps, with time, you will grow to appreciate what he has to say, and why he has said it.

  • Except that this is not a problem with X fonts. The website actually gives fontsizes in pixels, so the 10px text will look miniscule on any high resolution display (I run my 17" monitor at 1280x1024.) This is pretty indecent for someone who claims to be a webdesigner.
  • Do you ever wonder if OOG and JonKatz are the same person? Scary thought, isn't it?

    cheers,

  • She says it herself, "I have never created a Web site other than our own."

    cheers,

  • Lynda: Open standards, open source, browser compatibility and cross-platform compatibility. A tall order indeed.

    I wonder why Lynda Weinman think's this is a tall order. Perhaps the following might give her difficulties some context:

    Lynda: What's screaming hot right now in the way of technologies is Flash.

    Although she admits that Flash has "challenges" in areas of "accessibility and interaction with other Web technologies" she seems to give no advice about utilising the real benefits of the WWW.

    She might sing a nice song about Open Source and a cross-platform WWW, but until she demonstrates some understanding of the concepts, newbies beware.

    Lynda: We develop our own curriculum and courses in Dreamweaver, Flash, Fireworks, ImageReady, PhotoShop, GoLive and are about to expand into Final Cut Pro, After Effects and LiveMotion.

    Quite what her courses have to do with her excitement with XML and "devices other than Web browsers delivering Web content" I have no idea.

    Calum
  • Presumably because she cares about typography, and there's no way in hell that a markup language is going to give you the control of appearance that you need to do anything interesting with design.

    And exactly how many times did this wonderful advocate of Open Standards mention CSS?

    If Flash is the answer, then presumably the question is not "How do share structured information with someone on another computer, another browser, or another network?". That's a shame.

    One day people will understand what the WWW idea ("portable content") was all about. Of course it might be past salvage by then.

  • The best "PS for the web" is XML [w3.org] with XSL [w3.org]. XML for content, and XSL (extensible Style Language) to format the document. XSL can be used to transform an XML document into HTML, but it can also specify hard formatting, ala PS. It doesn't need to use tables to control layout. Very cool technology.

    The only problem is that this stuff is pretty new and no one's written editing software to take advantage of it yet. Stay tuned to the w3.org site and I highly recommend reading Tim Berners-Lee's Weaving The Web.

  • i remember being on a pr0n site on geocities where the perosn had thoughtfully put thumbnails of all the picture on one page with a click for larger version. Unfortunately they had simply used the full size image with width=100 height=100 in the tag. Very painful
    .oO0Oo.
  • How to prevent it? Easy. Force every web designer to view their work... with a 56k dialup.

    What's needed is a simslowconnection.com, which simulates a slower connection for a given web page. Thus you could send e-mail to a bandwidth-hog webmaster, saying "look at your site through
    http://www.simslowconnection.com/test.pl?page=ht tp://www.toomanygraphics.com
    and see if you still like using your page.
  • Specifically, what is Lynda doing that deliberately breaks cross-platform compatibility? Her pages looked readable in w3m under Linux, and that's good enough for me.

    Open standards and cross-platform compatibility *can* exist, but not enough people use it! There's a big difference between writing a spec and making people conform to it. Until the HTML spec is *better* than what Evil-Browser-X wants you to do, people aren't going to use it, and Conformant-Browser-Y will be broken.

    Therefore, a project like Mozilla is a step in the right direction: a great, spec-conformant browser with a fast engine that people can use for their own projects might cause people to write HTML with it in mind. (web browsers are like platforms for HTML) If so, the HTML would naturally be more spec-conformant because the browser is.

    In an ideal world, the W3C would put out the best browser, and the spec would be friendlier than anything a corporation can come up with. Do you now understand that we live in a far less than ideal world, the spec is a nasty compromise with big corporate interests looming over it, and Amaya is an ugly-looking, unpopular browser?

    Are you now wishing for people to use those darn open standards, and write pages with cross-platform compatibility in mind?

    I know I am. I'd rather use HTML and JPEGs than let PowerPoint mangle perfectly good images, but people like me are in the minority, and the majority has taken over the web.
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • At first I was somewhat dismayed, seeing that she writes books about Photoshop and Dreamweaver, and teaches courses on Flash, but then I saw this:

    Wendy: If you could have one wish, forgetting the practicality of whether it can be done, what would you like to see changed in the Web development world?

    Lynda: Open standards, open source, browser compatibility and cross-platform compatibility. A tall order indeed.


    Keep up the good work, Lynda! I completely agree with using tables to organize text properly.

    Oh, and the 216-color "web-safe" palette is obsolete: it has always looked nasty, all by itself!
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • Well, you have the wrong link, for starters.

    Try this one (Lynda with a 'Y') [w3.org].

    And yeah, it still doesn't validate, but the W3C Validator is strict, and pretty crappy too. And the CSS validates just fine. Pretty good, for a (probably hacked) "Adobe GoLive 4" generated page.

    And remember: Valid HTML might be syntactically correct, but that doesn't make it Good.
    ---
    pb Reply or e-mail; don't vaguely moderate [152.7.41.11].
  • What do you think about people who say that the web is for the most part a huge waste of bandwidth? There's a lot of people out there who really just want to revert to the primordial ooze of plain ASCII text gotten from archie/FTP or elsewhere, but the web is here to stay, complete with 300KB images that contain nothing but a picture of text that the web designer thought was in a cool (but browser-wise unavailable) font.

    What's the most hideous use of bandwith-busting graphics that you've seen, and how do we avoid the brainless design decisions that lead us down such evil paths? :)

  • She writes good books for beginners... and she does it right!

    Instead of saying, "this is an tag..." like SO many books do, she teaches web design from the perspective of creating quality websites. There are entirely too many "web design" books out there on the market that just shove some HTML on the reader and hint on design.

    Her books cover some great intro topics that allow readers to understand what makes a high quality website. Elements such as file format selection (GIF, JPG, PNG), and the use of tables for layout, and much more.

    I'd recommend her books as a great place to start for anybody interested in quality "web design".
  • It's an odd quirk of fate that made this woman famous. When Netscape put out the first version of Navigator, they chose to handle displaying multiple images with different color palettes on 8-bit color systems by dithering everything to a 6X6X6 color cube. This information was freely available in the support section of their site, although it wasn't obvious to look for it there. Check out the date on this technote:

    http://help.netscape.com/kb/consumer/19960513-14 .html

    Big-time designers fresh out of classes in multimedia made 32-bit images on their enormous Macintosh monitors and then wondered why they looked so bad on the web.

    In the multimedia company where I worked, I was the techie who learned about the web, figured out what worked by reading usenet and Netscape's technotes, and then taught the designers about it.

    After I'd been doing this for a year or so, Lynda's first book came out. It wasn't great, and contained a few technical mistakes about image formats and when to use which one (I don't think she knew much about how JPEG compression worked), but it gave some simple advice about color palettes that Photoshop jockeys could understand, so I happily let the designers learn the ropes from her book instead of me. A few months later, everyone had a copy of her book.

    These days, they all know this stuff cold. Of course, most people have better than 8-bit color now too.

    Sad to hear that she's promoting something as evil as Flash now. Maybe she should do a nostalgia tour with Laura Lemay, destroyer of trees.
  • Lynda's books are written from the perspective of someone who knows how to create images but isn't a webhead.

    I'm sure there are millions of webheads out there who are comfortable with the web and computers but have no idea how to even draw a straight line without help.

    I'm one of those people. I'd love a book that would tell me how to use Photoshop or Fractal Design Painter from the perspective (pun intended) of someone who needs to understand perspective and other drawing concepts as well. I feel I could have some great designs in me if I just understood how the whole art world works.

    So basically, I want a beginning art book that focuses on using drawing/image editing software to create great images, but that takes the time to explain image creation concepts in detail.

    Anyone know of such a book?

    D

    ----
  • The funny thing is: I do run xfs! And I use the 100dpi fonts! 90% of all web pages display ok. To have a "web designer" in the remaining ugly 10% is just ridiculous... She brags about 'platform interoperability' (sp?), so she's either clueless or a b...

    Sorry, but this really pisses me off. I've had to mug around with my CSS to circumvent the buggy IE implementation (/span/ tags...), although I'm running a site aimed at Linux users [mandrakeuser.org]. Because I care about users who use other OSes (even if it's Windos ;-)).
    Why someone like this gets an honorable mention on /. is beyond my whatever (like so many things, sigh... ;-)).

    Regards and thanks for your tips

    tom

  • Nice page you've got there, a real asthetic sense behind it all. You don't seem to be interested in publishing as an art form. I can't think of anyone who draws or paints in Braille, it is unfortunate some people lack the sense of sight but that doesn't mean I need to cater to them all of the time, especially in publishing design. Do you bitch at magazines for printing pictures on their pages that blind people can't see? What about CDs, are you boycotting them because a deaf guy isn't going to be able to listen to them so no one else ought to? Being as blatently ignorant I doubt you can grasp the concept of HTML, it was NOT designed for publish. HTML was designed to present and organize text. Because of it's simple rendering requirements it became popular and easy to use on just about any terminal. Go blow your rant out your ass.
  • Wow, I remember the web looking akin to Yahoo!, very few if any graphics and just really basic HTML script. There wasn't a great deal of styling but that was alright because people for the most part designed pages well. Now pages take several minutes to load on a 28.8 modem. I designed my site for small pipe connections. Before the SSI all the pages or only about 6KB with a 27KB title picture (yeah it'd be smaller if it were a GIF). The actual size of the page depends entirely on how lazy I've been that day/week/month. It's tough now to make pages that can be viewed well in every different browser and OS. All of the HTML except for the very small amount of scripting is all standards compliant. I don't bother with making it fully compliant with every browser because the lack of the scripted effect won't change the look or layout of my page.
    Web design right now is going through the same birth pangs that desktop publishing went through when we were first able to change the font and layout of a page. Some people go ape shit with fonts, colours, and images until their page is unreadable. Others go for an austere look that doesn't convey a sense of creativeness. Then of course is the medium range that isn't either of the extremes. What I would like to see something like PostScript for the web. HTML is being extended past the point of its usefulness as a publishing form. Remember HTML was originally designed for indexing large numbers of files in an archive, not driving sites like MSNBC. Whenever I do any sort of publishing I export it to a PDF (gotta love PDF) so none of my formatting or design is lost. This is mostly for my benefit, I'll take docs down to Kinkos to borrow their laser printers and I don't want to mess with the incompatibilities of word processors. Wanting a PS-ish language for the web is asking a bit much, afterall HTML is incredibly easy to render (hence it's initial popularity) but I think something new IS needed.
  • I visited your web page, and I think you're just bitter because you have one of the ugliest web pages known to man. Perhaps you're taking angry potshots at people who give their pages an attractive design because you have no such aptitude?

    I'm interested in replies from anybody who has visited mill's web page [sn.umu.se] and thinks that his is a voice worth listening to on the subject of creating web pages.

    Cheers,
    ZicoKnows@hotmail.com

  • If we're going to make recommendations for web site design, how about this one single chapter from Philp Greenspun's "Philip and Alex's Guide to Web Publishing": Learn to Program HTML in 21 Minutes [photo.net]

    Also note that Greenspun walks the walk. A nice, simple layout, wrapped around some nifty photos presented in an easily digestable thumb-nail format. My only complaint is that he uses white backgrounds as a default. (I will never understand why people do this... It's a computer, it doesn't *have* to look like paper, and having a CRT shining it's high beams in your face does not make for a pleasant reading experience).

  • I too checked out her web site. And was amazed about how non-consistent a web-page may be. Not one page looked like the other. I do not say pages has to be exactly the same - that would be boring. But they need to share some common design ideas so that they may be cognished as a whole.
    Secondly, she seems to have forgotten about compatibility - her site is not even (as you mention) optimized for a specific window size, btu for a specific OS. She has not shoosen any "fallback"-fonts, thus the default is used, which with her font-sizer setting gives totally unreadable text under most UNIXes (And probably Mac too, and Mac users who are so daring about look!)...
    As to your comment about tables: Tables are much much better to format the text and create coloured blocks, than the zillions of pictures used on many web sites, so there she's finally right...
    --The knowledge that you are an idiot, is what distinguishes you from one.
  • Imagine trying to navigate Slashdot without any images or tables or little boxes to organize everything. You'd very quickly go insane, or at least stop visiting.
    Exqueeze me?

    Slashdot is not about all the little boxes. Matter of fact, CNN is the only little box I use on a regular basis.... and it could be replaced by a link at the bottom of the page.

    Slashdot is, as a matter of fact, about content... and, as the previous poster said, about moderation... not in graphics use, but in the readership weeding out the AC's from the juicy tidbits. If all I had was a steenking dummy terminal and 2400 baud, I would still read Slashdot, although all those little boxes would surely go bye-bye.... Thanks to Taco's excellent customizations, mostly with one flick of the spacebar. (q.v. "lite mode") (I would probably also run the threshold up another notch, and decline to moderate.... weeding thru 100kb of AC flamage isn't nearly as much fun when your download speed is within an order of magnitude of your reading speed as when you've got a significaant fraction of a megabit for a pipe....)

    No, the problem is that the Microsofties and the Netscape/AOLs of the world (a plague on both their houses for this) have convinced all the newbies that a world devoid of flashy grahpics and megabitpipes is one not worth living in. Politely put, bullshit. One can live just fine at 2400 baud, no graphics, dummy terminal. I did for many years. It's simply a matter of picking sites with minimal fluff and maximal real content.... like Usenet used to be ten years ago. Matter of fact, some places on Usenet are still very useful. Even better, what about mailing lists? Those don't generally have graphics (although I can't say that for a number of better-known MUA's :), and still manage to be extremely useful.

    Slashdot unusable without tables and little boxes. Puh-leeeze. Admittedly there is a good portion of the web that does, in fact, stink when you have your images turned off. Even my own ISP has a major problem with overgraphicsitis on some pages, and those guys are otherwise cool as a dewar full of liquid nitrogen. But we went thirty years without requiring a graphics-able terminal in order to do useful things in cyberspace, and we're not bloody about to start now.

    --
    I remember when we had 300 baud and liked it.

  • 1) no font tags. It slows download times, bloats filesize, and holds no weight for the colourblind. If you want to make colour or font size changes, be uniform -- use css to make certain pages are readable with/without your changes. My page [lm.com] is an example of css not going overboard.

    2) no frames, unless you handle them right! Set targets! If someone hits back, It better not take them to the top of your site!

    3) Indent paragraphs the way they should be -- with a <P>! Use a "text-indent: 20px" to get the appropriate result. Non css (that is, 2.0 and lower) browsers won't recognize this, but the result is not important at that level. It will still have a clear break. I have personally converted a <br> &nbsp; &nbsp; &nbsp; Text to a <p>text <</p> pair and saved 10 k off of a 55k document! Each tag went from 25 bytes to 7!

    4) Break up tables. Nothing is worse than going to a page like stileproject and waiting for a half hour for it to load. break things down as much as possible. Not everybody is on the campus net, or on dsl.

    5) keep all pages, unless they are about graphics or media, under 25k. most of my pages weigh a measly 2.6k. That is because I don't use images. I designed a portal template that takes at most 4k. Adding stuff later won't be much a burden on the webserver or the user that way.

    6) finally, use xhtml where available. This way, you have validated code, and little handheld web devices can grab your data in the future.

  • Mine's all the above and worse :)

    Colour choice: go for contrast any time. I prefer dark backgrounds with light text, too, and find (for example) standard M$loth-produced black-on-bright-white painful to think about.

    Widths: no-one in their right minds browses at 800x600 "full-screen" whatever that might mean; and to press the point I *like* something that resembles an A4 page in aspect ratio, with minimum usable browser-"isms" at the top.
    So any page that pushes its content off the right and gives me a horizontal scroll-bar is out of the question. (It boils down to using "width=90*" in your tables, for example. Or better yet, not using tables at all.)

    Front pages: the "click here to enter this site" stuff is abhorrent. I entered the URL, so give me the content. I do not want a "web-surfing experience", surprisingly enough.

    Javascript: don't bother, it's disabled. I find too many sites out there abuse it with gratuitous pop-ups and stuff (even whole new browser windows) to bother with it.

    Images: ALT attribute or forget it.

    Broken mime-types: do NOT do what themes.org do and make everything a CGI-link to the file with a perverse mime-type. If it's closest to "octet-stream", send it that way and I'll handle it - that's my problem. If you give me the filename I'll be able to download it in bulk mode later, or use shift+click to force a download. Honestly, people who expect left-click to do everything for them... *sigh*!

    Let's remember that the Web is a document-dissemination medium and how it looks is determined by the browser, NOT the other way round. If you write valid HTML then there's no excuse for folks not to be able to read it - after all the rule for browsers is, "if you don't know the tag, ignore it and don't lose content", which allows a site designer to adopt the approach of "valid HTML+CSS" instead of "works OK on all but 20% of browsers".

    Roll on the W3C [w3.org] and DOM [w3.org], any day!
    ~Tim
    --
    .|` Clouds cross the black moonlight,

  • Yes, but you have to concede that font management on X (or is it Netscapes fault?) is crap. I had the similar problem with other sites. The solution was to get xfstt [unc.edu] (a free truetype font sserver for X), setup and create a link to my windows fonts directory (yes, I dual-boot... Falcon 4.0).
  • readibility (and quick/easy access) IS the number one reason for the web right? If I wanted arty shit I'd go buy a book on design....

    Yes, readability and easy access is king, but I was referring to the wonderful standards-compliant code of the page. It even degrades gracefully with alternative browsers (VERY readable in Lynx). This guy knows HTML 4.0, period.
  • Oh I got it now... Had a look at the source, the font sizes are defined in pixels! hehe.

    OT: Nice site. Coincidentaly, I was just downloading Mandrake right now, and I'll come back to molest you with my install problems in about 3 hours ;)
  • I've read Lynda's books and they're really good for beginner - intermediate designers, but kinda' are redundant once you know what you're doing. That being said, she's a kick ass person and a Mac person as well. (iirc, she worked electronic pre-press long before.)

    ----
  • Kind of an interesting point, even as a lame troll. But you missed the boat completely, anyway. The only reason you have the 90% margin to shoot for, the only reason you have any idea whatsoever as to what constitutes ACTUAL use is because someone gave you a standard in the first place with which to measure your deviation.

    Without the standards nazis, the RMSs, the detail sticklers, and all the other inflexible bastards in this world, there would be no room for your mostly-compliant pages that work only because browser makers have coded their rendering engines forgivingly enough that you can get away with it.

    Without standards, there is no Internet. Without the W3C, there is a power void filled by any self-serving corporation in whose interest it is to see the "standards" bent their own way. Without a detailed specification of the way a markup language should and should not behave, you have no common ground off of which to build.

    Interestingly enough, the reason you have to design for what looks best, works best for the majority of browsers, and gets the job done, with compromises in each of those areas, is because the standards were not implemented as spec'ed, forcing you into work-arounds to the Nth degree. As content as you may be with this bizarre stretch of HTML, it is by no means a utopia, nor is it the fault of the W3C.

    Standards are your friend. Learn it, repeat it, live it. Not that your post was anything but a crude attempt to start a flamewar, but it was too stupid to pass up.

  • Say the magic 'O' word and all is forgiven! I'll say it too: open-source. open-source. open-source.
  • However, Open Source goes a long way to helping out the other three goals: if you can simply recompile, or patch the source, what could be more open and friendly than that? It's additional and optional, and programmer-friendly. No one else should care, except that they might get an enhanced product out of the deal. But we'll see how Netscape 6 is soon enough...

    I'd like to hear about web design, as in the design of usable and aesthetic web sites. Not more open-standards/open-source rah rahing. Turning everything into yet another hymn in praise of open-source is extremely boring, and saying that she's cool and you like her just because she's smart enough to say that she likes open source in an interview is extremely superficial.

    btw, I moderated the other post you were talking about down as redundant (the moderation was undone after I posted of course), because it really doesn't contribute to the discussion. To get moderator access, you need to post/reload less often Slashdot - I haven't been reading Slashdot much the past few days so I've some moderator points now.
  • Well, in web design, as in almost everything else, there's a happy medium. You're right, alot of the graphics and scripting and whatnot that are put into websites are fluff. But they aren't all bad. Imagine trying to navigate Slashdot without any images or tables or little boxes to organize everything. You'd very quickly go insane, or at least stop visiting.

    It's all about moderation. And compatibility, which is really the hard part, even though it's not really the fault of the web designers...once again, just look at microsoft

  • I've never even heard of Lynda Wienman, or her books, or even her website and I've been making webpages since '95 Just paid a visit to the site - what's the big deal ?
  • Well webpage layout and techniques are being used everywhere. Let's contrast CNN [cnn.com] and Attrition [attrition.org] ... both are fairly visted websites. But attrition relies on what it writes unlike CNN that relies on images....

    The real question is ... how much more impressive is an article about potatoes with images tables javascripts php perl cgi and whatever ... compared to the simple bare-minimum html page with nothing other than black text on a white background. The article doesn't change ... The potato still grows ... so what's the need for extra space? People like eye candy ... just look at microsoft.

  • I agree, her pages look like crap and are technically flawed. I don't know what her (alleged) credentials are, but I won't be buying any of her books anytime soon.

    Anyone interested in designing usable cross-platform web pages should check out Dr. Jakob Nielsen's website UseIt [useit.com]. Wonderful content, textbook-perfect cross-platform html, but [IMHO] ugly as sin.

    Another excellent site with more of a hands-on, tutorial approach is All Things Web [pantos.org]. Very good content & asthetically pleasing to boot.
    "The axiom 'An honest man has nothing to fear from the police'

  • I'm interested in replies from anybody who has visited mill's web page and thinks that his is a voice worth listening to on the subject of creating web pages.

    Yep, he is. As others have observed, he knows his HTML - it's pretty close to perfect. He has some interesting quotes, too. I'm not fond of the shade of yellow he uses, but it's better than the vast majority of Angry Fruit Salad [tuxedo.org] pages out there.

    How about putting up an example of your own HTML, before you go attacking other people.
    "The axiom 'An honest man has nothing to fear from the police'

  • I want to elaborate on a point made in my earlier post, to head off some potential arguments before they start. (Of course, I may start a few more. Who knows? ;-)

    I had said that content is 95% text, and style is 95% graphics, and the WWW is optimised for content (text).

    Some people would say that fonts and text layout are therefore graphics fit into my idea of content. Those people are wrong. Fonts are collections of characters, which are graphics in themselves. And text layout is the physical positioning, spacing, etc of text characters. Text, however, is independant of its font and layout. You can take 10 point Arial in a justified paragraph and change it to 12 point Courier in a single line, but the text still has the same meaning. Text, meaning the ideas that the font characters represent, is independant of its presentation. My personal design philosophy is that content should always be independant of style, and never depend on it. If a user is unable to absorb the information from your website after he has turned off JavaScript, CSS, images, Java, and all plug-ins (ie Flash), then your site is a failure. (The same caveat regarding image archives applies.)

    The best test is to try viewing your site with a text-only browser, like Lynx. If you aren't able to communicate ideas effectively to Lynx, then you have either too much style, not enough content, or both.

    The old saying that "a picture is worth a thousand words" is true, if the graphics are properly appplied. Look at Slashdot. The site is mainly text, yet those icons for the story topics on the index page are very helpful; they allow me to grep the contents as fast as possible. But the graphics on Slashdot are acceptable because: if you remove them, the site loses no functionality. (In fact, I believe that there is even an option in the "User Preference" section to turn off those graphics.) Don't become dependant on graphics. To put it in a different light, graphics on the web should be frivolous, they should never be a necessity.

    (Yes, the caveat regarding image archives and sites whose purpose is to present images applies!)

    I looked at the link in the story description, about Lynda. She appears to be my idealogical opposite on WWW design theory. (She looks like a high-school art teacher; need I say more?) I read the bit about Flash (ugh) and Real... I don't think I'll be coming back to see her answers to this interview.

    Heil JonKatz!

    Signed,
    Anti-JonKatz Troll

  • by thenerd ( 3254 ) on Tuesday March 28, 2000 @01:52AM (#1166482) Homepage
    I agree with you wholeheartedly with your opinions regarding stylesheets. I do however take task with your comments on frames =)


    Another thing that really bugs me is the now-popular trend to make web pages look like printed pages; for example, with columns down the left and right of EVERY page of a web site with the standard menu of links. (Slashdot does this.) These should be in frames, so the body is a page in the middle frame with nothing but the body text in that HTML file. Again, accessibility is sacrificed for appearance, and in a portable, small-screen text-based device, it will be unreadable. A text-to-speech reader will not work on the page without reading the entire left menu column on every page.


    It turns out frames as they are used now would not actually be that good for a small windowed browser - here's why. With a framed site on a small screen, either

    1) The person designing the site will have assigned a percentage to the navigation part, and a percentage to the content part - in which case, if they use graphics in the navigation part at all, they are liable to have scrollbars inserted there (because if they didn't the whole thing couldn't be viewed) thus rendering the site horrible (requiring to scroll to see design graphics) or

    2) The person designing the site will have assigned a fixed value to the navigation part, and what's left over (or some arbitrary value) to the content part - in which case one part of your screen renders OK, and what little there is left of the rest you have to navigate painfully due to the size of your screen.

    In addition frames are a bad idea due to the inability to say to someone 'hey, check out this URL' when referring to a framed site. If I want to email you a URL of a site that uses frames, I can't. I can either email you the URL of the original frameset, and say 'navigate to page X', or I can email you the URL of X, whereupon you will miss the navigational aids.

    However, most of your post I'll agree with. Accessibility is good, and it seems there's a lot of work that disregards it. I guess it's easier not to know how to do something and get on with it anyway.

    thenerd.

  • by pen ( 7191 ) on Monday March 27, 2000 @09:29PM (#1166483)
    Is this the same person who owns Lynda.com [lynda.com]? Has anyone visited the site? Allow me to summarize it for you:
    • The layout is resolution-dependent, and the sizes are hard-coded. It will not reflow to adjust to higher resolutions.
    • The colors really hurt my eyes.
    • Images are used instead of text, without ALT attributes. The same goes for images that link to stuff.
    • The page looks like crap in anything besides the two major browsers. Just try it in Netscape 3.x or Opera.
    Isn't this exactly what most web design guides advise against? Granted, the other pages [lynda.com] look different, but the main page still breaks every design rule I can think of.

    And does the logo remind anyone else of an SUV-driving earth-loving vegetarian snob? :)

    --

  • by Witt ( 22760 ) on Monday March 27, 2000 @07:56PM (#1166484) Homepage
    I think one of the most valuable skills as a web designer is actual design training / skills. Even though someone with design sense may not know exactly how to get what they want using HTML, many geeks who know HTML inside and out can't come up with elegant designs for their sites.

    When I look at a website, I want fast, simple, clean, and content driven. I want to read what I want. I want to find it easily. I want it now.

    What I don't want (and what I see more often than I'd like) is ugly, hard to read, , etc. Not to mention that I often have trouble finding what I want on a site. Good HTML skills are useless if you don't design the site well to begin.

    Design sense is easily the most important ingredient in a good website after content.
  • One thing that is often forgotten about HTML is that it is intended to define the structure of a document, not its presentation. That is why elements and attributes controlling appearance (color, alignment, etc.) have been deprecated in the HTML 4 standard. All aspects of a page's presentation should be in style sheets. This maximizes accessibility. (See http://www.w3.org/TR/html4/intro/intro.html#h-2.3) With this design system, if I don't like the wasted space of a 3-inch column of text going down my 12-inch wide monitor, I can disable the style sheets and view the text from one side of the screen to the other.

    Another thing that really bugs me is the now-popular trend to make web pages look like printed pages; for example, with columns down the left and right of EVERY page of a web site with the standard menu of links. (Slashdot does this.) These should be in frames, so the body is a page in the middle frame with nothing but the body text in that HTML file. Again, accessibility is sacrificed for appearance, and in a portable, small-screen text-based device, it will be unreadable. A text-to-speech reader will not work on the page without reading the entire left menu column on every page.

    I would never trust web design advice from www.lynda.com with their design philosophy. They don't understand the purpose of HTML, and make the types of mistakes I pointed out. (Of course, they wouldn't regard them as mistakes, they do it intentionally.) Also, look in the source of the front page; there's a script with a comment reading

    THIS IS A WONDERFUL LITTLE SCRIPT
    IT WILL BREAK ANY PAGE OUT OF FRAMES

    All that does on the front page is reduce accessibility ON PURPOSE. What the hell is the point of that??

    If a web page is supposed to have an exact appearance that will work only on desktop computers with large graphical displays, HTML is not the proper tool. You might as well make a big GIF imagemap with all the text and hyperlinks with only the minimal HTML needed to operate the imagemap.

    I wish more web sites would use HTML properly. The increase in accessibility would make possible such browser features as automatic table of contents generators (from the H1..H6 tags), collapsible outlines (from the OL, UL, and LI tags), and resizable tables. But they would choke on most major sites today because they abuse HTML. Perhaps the only way that web designers will change is when HTML software actually starts to take full advantage of the HTML elements.
  • I'd like to clarify something before I read another idiotic post complaining about "Perl and CGI" being related to the problem of flashy websites. PERL HAS NOTHING TO DO WITH THIS. All of that annoyance is mostly Flash, JavaScript, and Java. Perl, in contrast, is server-side, so you NEVER SEE IT, and also, it handles mostly text and database stuff -- in other words, the exact opposite of what you're talking about.

    JavaScript is actually a fairly nice scripting language. Not half as nice or powerful as Perl, but a tasteful, minimalist application of client-side JScript with server-side (if you use Netscape Enterprise) JScript can do some really elegant things. I really feel bad that JScript jas been delegated to doing mouseover image crap.

    Java, while nice for flashy applications on the client-side, and for general data-moving on the server-side (i.e. servlets) is nice, but the client-side aspects are still too slow and large for general use.

    And Flash... well, it's like Microsoft: good for games. ;-) But graphics are all it's good for. Even it it had the proper interfaces for use with large amounts of text, it's too slow.

    And you can argue with me if you like, but content is 95% text. Conversely, style is 95% graphics. The WWW was designed, and is optimized for, displaying content which is mostly text. Hyperlink theory (Yes, "hyperlink" wasn't always a buzzword. Hypertext is based on complex theories of database design and information evolution.) makes this obvious. Despite the efforts of many graphic designers to change this, text is still what most people go on the web to see. Pictures are nice, but are mostly frivolous, except in image archives.

    Perl, on the other hand, works behind the scenes. It compiles and stores information, parses HTML, and does the actual "legwork" that the fancy JavaScript/DHTML interface on your favorite e-commerce site makes so pretty. Perl is naturally suited for this, because of its intergration with the Unix environment, its RegExp capabilities, its interfaces to filesystems and networks, et cetera.

    Yes, I am a Perl zealot. Behold the Camel in all his glory. But I am also someone who is very conscious of UI design and theory, and of what the WWW is and isn't currently capable of being. That's why I look down on the Flash people and the 'client-side JScript is kewl' people.

    Speaking of annoying JScript, I was at a site two days ago that had used JScript to disable the right mouse-button function! If you right-clicked on a link, you got an error popping up in an alert box. I had to turn off JScript to open a link in a new browser window. Now that, folks, is disgusting.

    Thanks for reading. Heil Larry Wall, and as always,

    Heil JonKatz!

    Signed,
    Anti-JonKatz Troll

  • by Elyas ( 59360 ) on Monday March 27, 2000 @07:32PM (#1166487)
    It looks like people think Slashdot is interviewing her, which is not the case here. ANOTHER web page besides Slashdot has interviewed her, and a link to this interview is provided. We do not get to ask questions and the highest moderated get sent, so people/moderators please do not spend too much time coming up with good questions and moderating them
  • by Arker ( 91948 ) on Tuesday March 28, 2000 @12:26AM (#1166488) Homepage
    *Specifically, what is Lynda doing that deliberately breaks cross-platform compatibility? Her pages looked readable in w3m under Linux, and that's good enough for me.*

    OK let's take a look at that web page then. Try browsing it in Lynx. Now try it in Netscape with image loading off. It doesn't take an "expert" to set up a webpage that degrades gracefully when image loading is turned off or not available. Granted there may be cases where this is not practical - but for the majority (if not all) of her site it would be quite practical.

    Look at lynda.com/resources/inspiration/index.html - it is quite a good example of the site as a whole. First off it's a frames page, which is fine, but take a look at the noframes section of that page. The tags are:

    <noframes><body bgcolor="#FFFFFF"> </body></noframes>

    *cough* I think that pretty well speaks for itself.

    Another major design flaw on that same page is that the left hand frame (http://lynda.com/resources/inspiration/menu2.html ) a long list of links, each anchored to a graphic. These graphics are, in fact, simply obfuscated text, see for instance http://lynda.com/resources/inspiration/images2/col or.gif which is a gif image of the word color in a sans-serif font. The rest of the menu is exactly the same, it's just a series of gif images of text used as links, and to top THAT off there isn't an alt tag on any of them. This is a textbook example of how NOT to code a page of this type - and this woman is billed as an expert and a teacher for people building webpages!

    There are likely more errors on that page, but this is enough to make my point - 3 major design errors on a single page, chosen at random (or as close as I can easily come to random, I maximized that window, closed my eyes, flipped the mouse ball around for awhile and clicked.)

    1) The use of the noframes tag so as to completely defeat it's purpose is totally wrong - she might as well have just not had a noframes section at all, for the same affect.

    2) The use of graphics which are simply text is bizaare and pointless. It's the sort of thing I might expect to see from a "Proud Teenage Single Moms of AOL" site - certainly not from a so-called expert.

    3) Even if she feels an uncontrollable urge to use graphics of text, the lack of alt tags is utterly inexcusable. Since the graphics are simply text in disguise anyway, it would take no thought whatsoever to determine the correct alt attributes for them; color, background tiles, frames, navigation, rollovers, etc.

    I don't claim to be an expert, far from it, but I would be too ashamed to ever show my face again if I put such a poorly written page on the web. How much moreso someone who makes a living teaching people to write web pages should be ashamed of such a monstrosity!

    Particularly when the fixes are so easy - all that would be necessary would be to eliminate the gifs in favour of text, or at the very *least* to add alt attributes (which are a REQUIRED, not optional, part of the HTML standard anyway,) in the file menu2.html, and then insert that code in the noframes section of the main file! 5 minutes work, and if it were done then her content would be available to all. In the time I've taken to write this message, she probably could have fixed those sorts of glaring errors all over her entire site.

    I guess she thought it was more important to spend that time doing an interview to promote her book and talking about how much she is in favour of "open standards" and "cross platform compatibility" though.

    Hopefully this makes my original point crystal clear?
  • by Arker ( 91948 ) on Monday March 27, 2000 @09:10PM (#1166489) Homepage

    I just checked out her webpage and the interview. What I found is a bunch of just bloody awful advice for web designers. For slashdot to give this woman credence as an "expert" is truly shameful.

    Just off the first two pages I've already seen two really poor commands (suggestions would be a nicer word, but less accurate it seems) to her clueless followers - using tables to control text flow and designing pages for particular screen sizes, both of which are things that anyone that understands html would know better than to do. Check out this poll [lynda.com] from her site - the question is "What size browser window do you develop for?" and then to top it off "any/all" isn't even listed as a choice!

    Go here [anybrowser.org] if you are looking for good html resources - not to Lynda's site.
  • by OOG_THE_CAVEMAN ( 165540 ) on Monday March 27, 2000 @07:19PM (#1166490)
    OOG LIKE VIEWING WEBSITES, BUT GROWING ESPECIALLY DISGRUNTLED WITH LARGE CORPORATE SITES AND LIKE!!! OOG UNDERSTAND ATTEMPTS TO BE GRAPHICALLY PLEASING, BUT GETTING ANNOYED OF BEING FORCED TO WATCH OBNOXIOUS FLASH ANIMATIONS (E.G. FOX.COM), DEAL WITH PERL/CGI SCRIPTS AND JAVA/JAVASCRIPT POPUPS, AND HAVE VIEWING SPACE REDUCED BY FRAMES!!! OOG WONDER IF CORPORATE WEBSITES EVER ACTUALLY GO BEYOND SERVING AS BLOATED ADVERTISIMENTS AND SERVE AS INFORMATION SITES LIKE THEY INTENDED!!! SEEMS LIKE MOST CORPORATE PAGES ONLY EMPHASIZE FLASHINESS WITHOUT ANY CONTENT QUALITY!!! OOG WANT KNOW IF THIS TREND CONTINUE, AND WHEN BIG COMPANIES FINALLY, IF EVER, REALIZE THAT FUNCTIONALITY MORE IMPORTANT THAN GIMMICKY LAYOUT AND TECHNIQUES???

Our business in life is not to succeed but to continue to fail in high spirits. -- Robert Louis Stevenson

Working...