Okay, this is cool! Navigate via hand-gestures, using your web cam…
Great basic intro post from Stoyan regarding how to set-up, download, and extract data from the HTTP Archives database. Begin fascinating data building, now!
I’ll bet most of you think of JPGs as one of the least-interesting topics in the web, right? I mean, they’re so tried-and-true, what could possibly happen to make thinking about JPGs even the slightest bit interesting, right?? Well, it turns out that there is a tremendous real, and more importantly, perceived, performance gain to be had if you format your JPGs as progressive, rather than baseline (as most image software natively does). Sadly, not all browsers render progressive JPGs, well, progessively, especially mobile where it is needed most, but hopefully that landscape is changing.
And using progressive JPGs could be a good first step to making your pages load in less than 1 second. A lofty, but courageous goal we should all aspire to achieve.
And would you care for a side-order of image compression with your progressive JPGs?
With the now-familiar
nav elements in our coding lexicon, it is surprising that there is no semantic element to identify the main content of the page (though
article kind of does, but one can have many
articles, right?). So, it seems logical that we should have a
main element, what?
Every web developer that has ever touched
z-index has cursed its name. Maybe this article will help avoid your next cursing bout…
Ever think about the process of reading? Yeah, me either, until I read this article, now I can’t stop thinking about it… Thanks, 24 Ways…
A great reminder of what mobile is and is not…
The idea of using icon fonts has been getting a lot of traction lately, and it seems like the next step is using Unicode characters. Anything that boosts performance without hurting accessibility is good for me!