Several web application have launched recently with an invite system where you not only give them an email address to notify you but also reserve your username. Some even go a little further and ask you to connect with Facebook, Twitter etc. The latest one to do so is connect.me, which I signed up for when I had heard about it.
So you're a developer (you're not a developer? then maybe this post isn't for you, but feel free to read on), and as with most developers you spend a lot of your time looking up things on Google, Stack Overflow or various API documentation (API docs).
We recently built an HTML5 audio player for Tim Van Damme's The Box, a new podcast where he interviews people who make cool stuff. Tim wanted an HTML5 audio player on the site, and we put together some jQuery to hook up the player interface he designed. In this article we'll run through the code to explain how it works, covering a few caveats along the way.
Now that the stormy debate around whether or not designers should be able to code what they produce has died down, the new debate du jour is here! Or rather, it's back again. This one has been around before, and it's about whether laying out your CSS code on single lines (one selector per line), or multiple lines is better.
Sometimes we need to take our web apps offline temporarily (usually for scheduled major updates or emergency repair work), whereby regular users are shown a simple static page notifying them that the site is unavailable but still giving developers/admins full access to the site to test changes. Of course you could implement this in your application, but wouldn't it be nice if you could get your web server to do it all for you?