Upcoming Blog Changes

By  on  

The BluDice blog will be going under some major changes during the upcoming month, including:

  • Domain change to "davidwalsh.name"
  • Added "Tools" section, where I will provide numerous Web Developer tools to allow you to compress your CSS, HTML, and JavaScript, and much more
  • Custom design -- even I know the current one is awful
  • Blog posts with images and in-depth examples (I've been holding off on some cool MooTools stuff for the new design)
  • More personalized content -- the site wont be about my person life, but I plan to throw more of my own flavor into writing.
  • More reader interaction. I'd like to do a "mailbag" post from time to time, where you can ask questions.
Do you have any requests or ideas for the blog? Please share them!

Recent Features

  • By
    Camera and Video Control with HTML5

    Client-side APIs on mobile and desktop devices are quickly providing the same APIs.  Of course our mobile devices got access to some of these APIs first, but those APIs are slowly making their way to the desktop.  One of those APIs is the getUserMedia API...

  • By
    An Interview with Eric Meyer

    Your early CSS books were instrumental in pushing my love for front end technologies. What was it about CSS that you fell in love with and drove you to write about it? At first blush, it was the simplicity of it as compared to the table-and-spacer...

Incredible Demos

  • By
    Digg-Style Dynamic Share Widget Using the Dojo Toolkit

    I've always seen Digg as a very progressive website. Digg uses experimental, ajaxified methods for comments and mission-critical functions. One nice touch Digg has added to their website is their hover share widget. Here's how to implement that functionality on your site...

  • By
    MooTools Typewriter Effect Plugin

    Last week, I read an article in which the author created a typewriter effect using the jQuery JavaScript framework. I was impressed with the idea and execution of the code so I decided to port the effect to MooTools. After about an hour of coding...

Discussion

    Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!