Drupal’s Taxonomy system is one thing that sets it apart from many other Content Management Systems and frameworks. It is functional out of the box, providing beginners and power-users alike the ability to tag content, and even creates pages to show content by tag. In keeping with the Drupal mentality, the system is pluggable and many developers have built useful tools to expand upon the features offered by the core taxonomy module.

When working with various stakeholders in a project, there is the ever-present temptation to tell a client what he/she wants to hear, rather than what he/she needs to hear...the truth. While it is easy to commit to any given deadline that is requested, the results of over-promising on deliverables almost always ends with unhappy employees, and a very unhappy client. Generating a long-term project plan is can be like walking on a wire for a project manager, but it is important to set up all involved parties up for success.

It all started when our project manager Tom forwarded me a link to a cool CSS utility he had come across called the Holmes Markup Detective.
It essentially acts a markup linter and uses CSS to highlight places
where your markup is invaild, non-standard or deprecated and also
includes CSS based messages to tell you specifically what the problems
are. Immediately I recognized two things: one, this was a great tool for
validating your markup with visual cues, and two, it could easily be
ported to SASS. The initial port from CSS to SASS syntax (or SCSS more
specifically) didn't take long, but as my understanding and awareness of
Compass extensions grew, I recognized that was the best way to share it
with everyone else. And finally, as of today, it is done.

Integration pieces in development can be a mixed bag. On one hand, they can be intellectually challenging to implement, which is a valuable opportunity for any developer looking to push their own envelope.