I've put together a cheat sheet of some of my most-used keyboard shortcuts and hot keys. I use the crap out of these, and I can say they really save me chunks of time every day.

I spent a good chunk of time trying to find the best solution for controlling inventory on an Übercart I've been developing for a client.

The biggest issue is that by default Übercart doesn't stop customers from purchasing out-of-stock products.

You can speed up your drupal load times a bit if you compress or aggregate your css files. Drupal can do this for you!

Simply visit Admin > Site Configuration > Performance and enable Aggregate and Compress CSS files. Submit the page and check out the results. All of those @import() calls will be condensed and you'll notice just one css is loaded.

For simple websites it's handy to separate elements that are shared across pages, such as your header and footer.

You can clear the DNS cache on Mac OS X Leopard in the Terminal application.

Open a terminal window and type:

beer$ dscacheutil -flushcache

That's it. If it didn't work, then your network server probably needs its cache cleared, or the DNS just hasn't propagated yet.

Often when developing Drupal, you'll have multiple roles that you'll need to test. Generally, I'll be logged in on one browser as admin. I'll have another browser open for another role.

So I go in and make a change as admin, then visit the other browser to see how the change affects the other role.

Markdown vs Textile... this is a tough one. I use both pretty regularly, and each has its perks and weaknesses.

When to Use Markdown

I usually choose Markdown over Textile when I'm:

• Jotting down general notes
• Drafting client proposals
• Reformatting HTML content

Markdown is much easier to read during editing, even without converting the document to HTML.

If you've ever dealt with Dreamweaver based templates, then you'll know all it really does it insert static blocks of code wherever the template/library item tags are located. Dreamweaver does a pretty good job at this, but once sites grow to over 1000 files, it's a bit more complicated and time consuming to modify every page easily...

There's a line between embedding images in HTML and applying the image as a background image via CSS. I often see them used incorrectly.

It all comes back to semantic markup. Semantic refers to meaningful, logically arranged (X)HTML markup. The content on a webpage should be in semantic markup. It should be readable with or without stylesheets, or in a plain text browser.