1. HTML5 Boilerplate. Prepare for the coming of HTML5. Use this mini-framework. Heck, use this for XHTML. Contains lots of goodies, no matter your flavor of HTML.

2. ie7.js. A JavaScript library to make MSIE behave like a standards-compliant browser. I have yet to test it so, stay tuned, or give me your feedback. If it does what it promises, could be one of the best contributions to the web design community since a non-IE browser.

3. Google Font API. A must-have if you want to get away from the usual 5 or 6 web-safe fonts.

4. Easy favicon generator. Not only can you import your own image (select the resize option), you can touch it up pixel by pixel once imported.

5. My new favorite: PIE. The brilliant minds at css3pie.com have conceived of a method to quickly and more cleanly add css3 effects to a page rendered in an Internet Explorer. What wins me over: rounded corners.

Caution: there are TWO snippets folders. The default snippets are in applications/Adobe Dreamweaver CSX, while the custom snippets are found in your personal configuration folder. It’s the one in the personal config folder that you want to migrate.

The process and location of that folder are explained here: http://cookbooks.adobe.com/post_Migrating_Dreamweaver_configuration__site_settings-17658.html

window.addEventListener('load', function(){
setTimeout(scrollTo, 0, 0, 1);
}, false);

It’s simple to install, and it comes preinstalled with IE6. You don’t even need a serial number for XP. Just follow the steps on the page (they’re surprisingly straightforward) and you’re golden. The only thing that was even slightly tricky was configuring BIOS if your hardware virtualization isn’t turned on, but I managed with no problems, and I never do any configuration.

I never thought I’d say this, but “Thanks Microsoft for this helpful development tool.”

Installation page: http://www.microsoft.com/windows/virtual-pc/download.aspx

BIOS configuration instructions: http://www.microsoft.com/windows/virtual-pc/support/configure-bios.aspx

Anyway, once you are lucky enough to have a programmer walk you through it, or you manage figure it out yourself through trial and error, the setup process is not that bad, and is elucidated below.

1. After you set up your github account (pretty straightforward) go to your dashboard. Here you will find a list of your repositories, or lack thereof. Click ‘create a new one.’

2. It will ask you for the name of your project. Pick something descriptive–ideally, whatever you’re going to name the directory on your computer that will be the corresponding local repository. If you add spaces to the project name, github will insert dashes.

3. Once you’ve submitted this information, you are directed to a page with setup instructions. Follow it precisely, entering one line at a time into the terminal. You will need to download github onto your computer, if you haven’t already done so. Basically, your github remote repo has already been created, and in this step, you are creating a local version on your machine and linking them together.

That’s it! This process will have to be repeated for every repository you wish to host on github, except for the very first part of the instructions regarding downloading and initiating github. That only needs to be done the very first time.

I’m creating a different repository for every piece of JavaScript I want to share on github, and no joke, it takes about 3 minutes to set up.

Also, it is important to note that any child or descendant div will be hidden by default. However, since we can’t simply exclude the usage of divs within the tab panes (I want to be able to put whatever I want in them!), just put style=”display: block” on each descendant div.