[Helen]

I would also recommend bookmarking the above link for W3C......... When Building sites, it's good practice to run each page you code through the validator to check it complies to standards.

Also running it through browsershots lets you check how the site looks in some of the most common (not to mention some of the most obscure!!!) browsers

[JohnRoss]

Originally Posted by Helen

My advice, would be to forget the WYSIWYG editors, they do nothing but bloat the code.

'Nothing' is a big word, WYSIWYG editors have their role, not least that they are useful learning tools. And Dreamweaver is much more than a WYSIWIG editor. You can't maintain a site with hundreds of pages using a text editor, for example, it just isn't practical. OK, in an ideal world, maybe a designer shouldn't have to do that, but in the real one... Plus, it's the industry standard, you need to be familiar with it to take part in any team work / work flow. Would an employer even consider a web designer's CV which didn't have Dreamweaver on it somewhere?

[JMCDesigner]

Originally Posted by JohnRoss

Would an employer even consider a web designer's CV which didn't have Dreamweaver on it somewhere?

I don't think he's looking to promote himself as a web designer, he's just after getting a base knowledge to extend his skills a little bit.

[JMCDesigner]

If you just want to dip your toe into web design, don't get bogged down in dreamweaver. You're talking about learning a whole new profession. Just do some reading on basic html stuff, there's so many levels to web design its hard to know when to stop. For your needs just keep it simple. And decide what you are: Graphic Designer/Web Designer. A good book on html basics and notepad is all you need.

[JohnRoss]

Originally Posted by BubbleButt

For example one client asked at the end of production to make the site updatable and to be bilingual. I'm sure my face went white.

These are development requirements, not just design requirements.* If you're being asked to do this kind of stuff, you need more than just HTML and CSS. I quite agree with those who are saying you need to learn the basics, that goes without saying, I had the impression you needed more, and Dreamweaver is pretty damn useful.


*In either case, a client who changes the specs at that stage of the game is offside, not that that's likely to stop them.

[JMCDesigner]

I agree with John Ross' comments. Web Design is such a grey area for some clients, they expect you to cover the full spectrum of graphic artist to web development, programming, database management and even IT support/server security! I've seen too many job postings for basic "Web Designer" wage which need a knowledge of PHP, JQuery, PERL, print skills, Ruby on Rails, ASP, and well you get the picture.

You need to make sure exactly what it is you want to learn, stick with that and don't go selling skills you don't have. I'm always honest with the people I work with, tell them what I can and can't do. To be fair I've always found a solution to their problems (even if it mean't buying a pre-packaged app!). Sometimes you just can't accommodate everyone, you'll wish you kept to jobs you know how to do well, rather than see it all fall down and not knowing how to fix the mess!

[DougBarned]

Originally Posted by BubbleButt

Does anyone know of a good book that talks about web for designers? Stuff like web standards, different technologies, user experience etc... Not so much 'a how to create a website' book.

Thanks

Hi BubbleBut

Smashing magazine have just announced pre-orders on their long awaited book.

Also, Save the Pixel might be worth having a look through.

Hope that helps a little :)

/Doug