When it comes to Drupal I love entities. Entity display modes provide simplicity in managing how your content is displayed. I used to be hardcore "Fields only" when it came to using Views and displaying content. Yeah, it gives you more control, but it is a pain in the ass when you have to replicated your field settings multiple times (if you have to.) Wouldn't it be super easy to just say "Hey Views, render this entity!" and BAM it is all there for you.
I'm going to Florida Drupal Camp, and actually proposed a session on Rockin' Responsive Content with Panels Layouts.". It looks to be a kickass camp, so get registered and go!
I gave a presentation last month at Drupal 414 on building responsive websites using the Omega framework, and compared apples to oranges with version 3 and 4.
For quite a long time I used Aptana as my development IDE; but, as time went on I found it quite bloated and extra features I didn't need. So I gave Sublime Text a try since it's all the rage by those who use it. Sublime Text is amazing because it's so simple, yet extendable. At first I was put off by a few things so I figure I'd share my setup and packages to turn Sublime Text into your IDE powerhouse!
Looking to uninstall a Microsoft product? May want to check out Bing first ;)
Last Thursday we had our second Drupal 262 user group meeting on "Breaking Down Drupal." The goal of the meeting was to simplify and explain all of the terminology found in Drupal: regions, blocks, menus, nodes, taxonomy, and users. I'm posting a link to the slides that were presented that helped tie everyhing together.
Earlier today I created a new sandbox module on Drupal.org called "Omega Responsive Menu," and although I have Omega in the title, it should be theme agnostic. The reason I called it Omega Responsive Menu is due to the fact I built it for all the Omega 3 sites I have had to work on.
Right now two of the most popular open source content management systems are WordPress and Drupal. WordPress is very simplistic and easy to roll out, which is why there is nearly 80,000,000 websites using WordPress. Then you have Drupal which is a more robust content management system that needs a little bit more love to get things moving.
After a few months I decided to give Facebook Albums some love. With 2.0.4 I implemented WordPress's caching mechanism to cache Facebook API responses for better performance. Will it never occurred to me about clearing said cache if the widget or that post updates.
So now if you update your Facebook Album widget, it will clear the cache and reflect your changes (such as image limit.) Ditto goes for posts, anytime a post saves the plugin checks for the shortcode (<3.6.0 compliant ;)) and clears that albums cached output.