This is excellent! Its awesome to see yet another great set of resources for aspiring web developers. I am not very surprised that Paul Irish is one of the developers leading the charge on this. If someone followed through this list in several days I imagine that their proficiency would increase quite dramatically. I especially like the layout and the easy to follow steps throughout the website.<p>If anyone is also interested in another excellent compilation of learning websites. Another collaboration of web developers created this:<p><a href="http://w3fools.com/" rel="nofollow">http://w3fools.com/</a><p>It provides some excellent resources on beginning to learn HTML and CSS.
Move the Web Forward. Prior to that, remove the layouting bugs (horizontal scrolling, after scrolling to bottom and then back to top). Be a good role model
I'm all for this. A lot of developers I've met learned HTML and CSS back in like 2007 and their skills and understanding of new technology hasn't progressed since then. The web is moving forward, and you should learn some new skills.
Wonderful resource. Very helpful to see all the important info on this one page (and I actually like this design) given the panoply of disparate resources out there.
I'm all for this. Especially teaching others. I recently befriended someone from HN who's been asking how to code in HTML and CSS. I directed to my github account and have been writing little tutorials to answer his questions over email. It really helps you get a better understanding of your own skills when you teach it to others. I'd also much prefer someone ask me directly than reading some tutorials online. There are so so many tutorials online that are teaching people the old, non-standard way of doing things. Basically, it's like all the tutorials from 1997 somehow get the best rankings in google for "HTML tutorial". Though it is important not to overestimate your skill level and hopefully you aren't passing along bad practices and techniques to others.<p>Other ways to move the web forward: stop supporting Internet Explorer altogether. That browser needs to stop being coddled and forced to get with the times. The difference between Webkit and Gecko rendering is almost a non issue but when you start having to support Trident then it's almost like having to code a site twice. Let's just stop supporting it and either let that thing die or force it to keep up. Version 9 and 10 are steps in the right direction but it can do better.<p>That said, we can't always drop IE support. Very high traffic, corporate, and intranet sites will still need to have support for IE for some time but all in all, lets drop it when it makes sense. Personal sites and even some business sites can work. I personally don't do anything to specifically support IE on my own business' website and it hasn't hurt me a bit. Let's take a risk here and there and drop IE support and move forward.<p>Moving forward is about more than just code though. It's also about user experience. A site with code that's 100% valid but is hard to use or uses distracting elements like gratuitous animations isn't moving forward. It's just building a site that looks like its from the 90's except with modern, valid code. That's lame.
This webpage is not available<p>Why the downvotes? DNS for this site was not working at the time this was posted. Possibly they just changed there IP and it did not propagate to all dns servers.
Interesting that the words "Microsoft" or "Explorer" don't even appear on the whole page.<p>Whatever your opinion on either, ignoring their existence completely is not going help "move the web forward".