5 ms·
To get a website up and running, most of what I listed falls indeed in the 20% category (80/20). But if you care about accessibility, usability and SEO you sho
by blauwbilgorgel 14y ago
To get a website up and running, most of what I listed falls indeed in the 20% category (80/20).
But if you care about accessibility, usability and SEO you should probably care about HTML issues like pagespeed and validation.
Web Content Accessibility Guidelines 1.0
Create documents that validate to published formal
grammars.
http://www.useit.com/alertbox/response-times.html
Users still hate slow sites and don't hesitate telling us.
Google Webmaster Guidelines (Design & Content)
Check for broken links and correct HTML.
So perhaps it is the "shit nobody, but front-end engineers, should care about" category.
- iand 14y agoLet's be fair: this is a 6 week old project to reconstruct Digg from scratch. In another 6 weeks most of these HTML problems will be gone. Also, I'm pretty sure they will figure out how to rescue those 14M 404s
- johnbellone 14y agoThat's not the point. Why rush the release when you know that historically Digg had problems with losing people because they severely botched a redesign? Didn't Digg at one point purge their comments and there was a huge uproar? The new management shouldn't have went online without the migrated data, or at the very least, the user profiles.
- iand 14y agoThey went with a minimally viable release and already have tons of feedback that, if they listen to it, will make Digg a great service again.