I can design the webpage..... i can convert PSD to HTML But all i am missing HOW TO MAKE MY WEBPAGES "W3C Valid XHTML 1.0"? plz advice...
Well, without knowing your current coding level or anything, I'd say, you need to simply learn more (x)HTML. If you know the rules, and what you may and may not do, you will be valid. Of course, valid code is only the beginning-- it also needs to be good code, but that's later. Mostly, you start out with a proper Doctype. Then you can send your page to the W3C Validator. It is a dumb machine. It will tell you where your code is wrong, but it cannot tell you if your code is GOOD. Still, fixing the errors is better than nothing. However, some things will "fix" an error, but is not the correct thing to do. This is where actually knowing HTML and how it works comes in. If you read the specs then that helps, though I find myself also learning a lot from articles on the web about topics like image replacement, accessibility, semantics, standards, etc. Some sites with decent articles (the ones I know about anyway): 456bereastreet.com htmldog.com alistapart.com tyssendesign.com sitepoint.com thought there are a bazillion others, but sometimes you read about an HTML element and want to know more about it (like, should I use it for this situation?) and I find reading what other people say about it helps me make a better decision. Hope this helps. (oh and everything I said about HTML holds for XHTML... there's really no reason to use XHTML except habit, or because the X makes it look sexy : )
Instead of constantly reloading in the W3C Validator, you can run a Firefox plugin like the excellent HTML Validator by Marc Gueury. There are plenty of things that will create invalid html - Flash, simple JavaScript mistakes, messy aff links containing "&" ... the list goes on. Once you get used to spotting the most common 'invalid' errors, it all becomes very simple to fix - dare I say it's almost fun (well maybe not for everyone). Pity it doesn't impress the chicks I don't think I could hand code a valid HTML document these days, XHTML seems so much more natural to me now. There was a reason I that I switched, but I've long since forgotten it.
Ah, sure you could. Take the closing /'s after the empty elements off, remove xml declarations in the <html> tag and you're usually set. A few small things would get caught, like if you had a fieldset not immediately followed by a legend (funny, the specs don't say anything about this, but the validator will tell you-- HTML4 only, not XHTML...) As for FF, I've got my 3 plug-ins and won't be burdening the poor thing any further.
Just out of interest, what are the 3 FF plugins that meet your approval? You really should try the HTML validator plugin - it's very light, and it gives you a BIG GREEN TICK when you get your page valid. It's good for the ego It's also interesting to see the amount of errors in other peoples sites. Install it, try it, and if you hate it, uninstall it. It's the first addon I install whenever I reinstall FF on one of my PCs.
Ah, since I always have access to the w3c one, I haven't installed it... FF is very memory hungry beast and some of the plugins really tax that (including... the one that's supposed to make FF faster! I forget, Fastfox? Some silly name). If I were born an Opera user I'd have it as part of the browser by default : ) I think if I had to validate pages with no Internet connection then the plugin would be worthwhile for me... but as my Fake IE64Linux can't look at local files, I have to upload all pages to a server for full testing anyway, so I must has teh internets. My three plug-ins are actually 4, whoops: Web Developer ToolBar Aardvark (this isn't actually very high on the list, just kinda fun) NoScript Window Resizer (I thought it came with the Toolbar but it doesn't). I have a Windows machine that I can set to 800x600 resolution, which is better, but for fast checking that something fits on a 800-px screen, the resizer is just so easy. I may consider Firebug... maybe when I start writing Javascript. My husband just used it today to find an image on a site... I knew the address of the image was in a folder further up the tree than the HTML page... I couldn't find the path, nor could the Toolbar, but my husband could find it with FireBug. So, I may consider it. But haven't needed it. Another reason I'm leary of adding too much bs to this FF is that it's the old 1.5 verion for Debian... they dropped support, I hated Iceweasel, and am just waiting until my new machine is ready to go back to FF2 or 3. Yes, I test in a buggy browser : ) But it's actually helped me catch more bugs because it's less tolerant of widths being a bit off than FF2 is... letting me tighten my code sometimes. Not so much nowadays.
http://validator.w3.org/ Use that to check your website, it will analyze it and tell you where the errors are.