I would much rather see those seeking to learn more going to the real W3C wiki-based learn page (http://www.w3.org/wiki/HTML). I see from this discussion how passionate people can be about presentation and learning styles. Once you get beyond the learning phase I recommend sites like SitePoint (http://reference.sitepoint.com/html) and Mozilla's Developer Docs (https://developer.mozilla.org/en-US/docs). I use these sites all the time.
edit: site is nice though.
The purpose of this curriculum is not the be-all and end-all of all HTML & CSS learning resources, it is focused on created a pathway that students can use to measure their learning. We are definitely focused on improving the curriculum and providing alternative resources for students to the learn from all the other resources.
I wouldn't be where I am in my front-end development without all the free and paid resources online devoted to HTML & CSS, but it would have been really helpful to have something as organized as this to guide my development.
They do offer a better layout and design imo and seem to be fine for the beginner.
However, everything can be better, so we will make sure to make the language and the flow can work for anyone.
As of now, this is the best standalone resource, but it is a couple weeks old, so we will definitely improve it.
Seriously tho, http://screencast.com/t/Qunx72f4rJC I know these aren't ready yet so they're deemphasized, but I'd like to be able to read them anyway. :)
Second. I can read them pretty nicely on my computer. It is clear a lot of work was made to make this website very nice. Your comment is a bit harsh.
Third, you are on HN, you should know how to read the code without being angry.
One thing you said does, in fact, really irritate me: "I can read them pretty nicely on my computer." This is not the standard by which accessibility is judged!! It doesn't matter if you can read fine in 7px grey on gray, that doesn't make it accessible.
I'm not just pulling this stuff out of thin air, by the way. http://www.accesskeys.org/tools/color-contrast.html These are widely accepted best practices, and you should follow them if you care about people with abilities different than your own being able to use your site.
Sincerely, it wasn't a personal attack. I am just sad a short comment about the look & feel make the top instead of a comment about the content.
Even if in the end, I tend to agree with you that this color contrast is a design error.
ps: Also, if you visit my website, you will see I am fully aware of accessibility and try to take a good care about it.
In the end I think it's important to remember that even if the content is the best thing in the world, that doesn't mean much if people can't read it. I'm probably just a curmudgeon but I've clicked links to posts where I saw the contrast and size and said "I'm not going to bother reading this. It is too hard and I don't care enough about this article to change my browser settings to correct the designer's mistakes." And many people don't have the skills to do so. Three cheers for agreement! :)
I am pretty sure you know about these, but just in case.
To address this problem I used readability from arc90.
Now I use a solarized[^1] version of readable[^2].
[^2]: http://goo.gl/jISPf => will go to http://readable.tastefulwords.com/ with solarized theme (my tiny contribution).
"this kind of comment about the appearance of a website should be done by asking directly and nicely to the author"
Given the site has been posted to a public forum, it's useful, both for the author and for other designers, to get a feel of how the community (read into that what you will) feels about a design, rather than simply one individual's private perception.
I also agree, however, that I personally don't see it as a major issue (I've included this statement to validate my original point - how meta...)
It feels like it's half guide and half reference, but not particularly excellent at either.
Also the organization of content seems way off to me. In the first lesson I learn about things like code validation and CSS resets, but I don't even learn about html list elements until lesson 9?
I think with a lot of reorganization and better 'chunking' this would be a lot better.
Nailed it. The site is is the foundation of Shay's weekly lecture, and in class, we have students do exercises where they incorporate what they just learned. We also have students demo what they built to the class.
The pacing is still a work in progress, we do our best to make sure that we aren't flying over the students heads too much, but we know we can do better.
This is wonderful, useful advice to beginners and seasoned developers alike. In fact, anyone who works with CSS, regardless of how they write it (raw, sass, less), should be force fed this advice. At the end of the day, CSS is a declarative cascading language, and you must leverage it as such in order to optimize code reuse, performance, maintainability, etc.
Aside from this tutorial being beautifully designed, the notes about semantics and best practices are enough to make me feel good about recommending it to anyone who wants to learn more about HTML & CSS.
Each lesson has its own key terms that can be used as a mini nav within the lesson which is helpful.
The code layout is simple and not overwhelming. Its nice to see long hand vs short hand
People can argue all day long about the right content but this seems to be a great start. Clearly the author has put much prep and time into considering this.
tl;dr; The lesson is pretty poor. Sorry.
It has a pretty small font size and for any modern monitor slides to the left and only takes up 50% or less of the page size.
This is why systems like LaTeX default to wide margins and narrow columns.
Now, as for the font size, it could definitely use some expansion.
Thanks for this beginners guide. It is very helpful!
"Elements are designators that define objects within a page, including structure and content. Some of the more popular elements include h1 through h6, p, a, div, span, strong, and em."
It's friendly to people who have prior experience, but I wouldn't give this to a fresh beginner. What's "content"? What about "objects"? I'd like a beginner's guide to introduce the reader by pointing out what each tag corresponds to on an actual web page so they can relate to it. It feels like a reference guide to HTML rather than an introduction.
Most of our students in Code Academy are "fresh beginners" and have been going through Shay's class for the past four weeks, and they have been improving greatly from the first day of class. They are currently learning web development, so they are definitely picking key concepts for Shay's class to help with their front-end learning.
From the above link
>If you want to stress importance of text, use strong. If you don't want to stress importance, use the b tag or use the font-weight:bold; style on the element or in the CSS.
Am I missing something? I've been writing html for long enough time not to consider myself beginner but it still doesnt make sense to me.
Now that we're back on track, If you're trying to make a semantic point in an article by emphasizing certain things, wouldn't you want that reflected in the HTML? Do screen readers do something special for bold-via-css or is the emphasis lost on the visually impaired?
No one uses WBR.