Good lineup. However, I think that #4 is only appropriate in beginner's guides—docs always should have some boring reference section with quick navigation. HTML5 boilerplate lacks that. Jokes get old fast.
Perhaps some good examples should be mentioned… I think, SproutCore handles points 1-3 very well (http://guides.sproutcore.com/), but lacks #5 a bit. Django's documentation seems to have most of these, too. (These aren't HTML UI frameworks, however.)
Sproutcore fails on another point though with making too much "improvements" on version 2.x. Why would anyone consider using sproutcore 1.x if it's already deprecated, and version 2.x is far from ready, as well as the docs. The sproutcore demos doesn't even work. You gotta have working demoes. There's no excuse for that - try getting your boss to accept a framework with no working demoes.
If you don't manage to get a home run with version 1.x just stick with it and fix the damn bugs, instead of doing the big rewrite, with the promise that it'll eventually work. It'll just work if you stick with it and fix the last 10%.
Perhaps some good examples should be mentioned… I think, SproutCore handles points 1-3 very well (http://guides.sproutcore.com/), but lacks #5 a bit. Django's documentation seems to have most of these, too. (These aren't HTML UI frameworks, however.)