One of the coolest features that made it into Drupal 7 without much (if any) fanfare is the Queue API. Drupal's Queue API is a pluggable system that allows you to queue events for later processing. Many systems, both in core (e.g., Batch API) and contrib (e.g., Feeds, Notifications, etc.), leverage the Queue API system.
If you have a content manager that likes to use inline images in the Body field of a Drupal site, you might run into an issue where they want an image inserted at the beginning of the field but don't want it to display in a teaser. Of course, you could tell them to use the "Summary" part of the body field to manually set the teaser, but some content managers tend to forget about that, and you're also dealing with an issue of entering data twice. No one wants to enter anything twice if they don't have to (even if it is merely copy and paste).
We've all done it. When we needed to find something in a log, we just did a cat or a tail and piped it to grep. Maybe we told grep to also show us X lines before and after what it found. That works fine and dandy when you've got just one or two servers. But what about 30, or 300, or 3000?
About a year and a half ago, I came across a post by Miguel Jacq about deploying Drupal automatically with Jenkins. I had grown tired of the manual backup->upload->test->crossFingers->pray->yellExpletives approach to developing or upgrading a Drupal site.
Every Drupal developer knows that there many configuration settings that are similar between the sites that they build, whether it's a personal preference or a trend among clients. And every developer that has been around Drupal more than a few minutes knows about the Features module.
A some already know, I have chosen to start hosting Drupal installs for clients. At some point (hopefully soon), I'd like to open this service up to the public. But that's not what you came here to read about.
I recently worked on a project where the main menu items were to be displayed as images. Of course, stylish menu items are usually displayed using text that's been styled with Cufón (or a similar solution) and using CSS sprites for the background. But in this case, there wasn't text.
Now, I could have worked on updating the Imagemenu module to work with Drupal 7, but there just wasn't enough time in the budget. So instead, I decided to use a hook in template.php to get the job done for me.
If there is a shortcoming in Drupal, its the way the menu system is handled. In this particular case, its that custom ID's for links added via the Menu Attributes module are added to the anchor tag and not the list item tag. While this is great for theming that particular link, it can cause difficulties when using most jQuery scripts to modify the display of your menus since the <li> tags won't have any identification.
You've finally gotten your Drupal website to the point where you feel like it is ready to go, but during final testing it seems painfully slow. With page loading speed a factor in customer retention (as well as search engine rankings), you need your pages to load as swiftly as possible.
I admit, I'm not much of a reader. Well, I take that back. I'm not much of a book reader. The super-dry stuff that people automatically hate like laws and the court cases that interpret them are pretty enjoyable for me. In fact, there's some cool little gems in a lot of them, especially when you come across a certain Supreme Court Justice that has no problem making sarcastic remarks in response to a lawyer's oral argument.