After trying out the concept I posted in My pathauto + menu utopian dream I found out there were some major shortcomings.

This entire post came about due to a great screencast by Addison Berry about using secondary menus. If you haven't already seen the screencast or you don't understand how to make the children of the primary navigation show up as the secondary navigation then you must watch the screencast.
I'll come out and say it, before watching this screencast, I didn't even know using the children of the primary navigation as a secondary menu was even possible.  I had always used the secondary navigation for things like footer navigation and created individual menus for the various sections of the site and placed each block.

Today I was working on a site when I noticed my node paths were incorrect for some of my nodes. Now I heavily use Pathauto in conjunction with Taxonomy to define my paths for everything on the site and this issue hasn't come up before. I swear, I didn't change my Pathauto rules ([termpath-raw]/[title-raw]), so what changed?

At this months Florida Drupal meetings a lot of questions came up about how we create websites. Now these questions weren't really about the technical aspects of creating the site, they were more about the planning and the high level steps we take.

... that is the question ... (Ok, I couldn't resist, I love puns and bad quotes)  A few days ago I was working on a site where I had created a content type that just mirrored the standard Page type (just a title and a body).  After looking at it for a bit I wondered if I should have just used taxonomy with the already existing page type to achieve the same effect.  I ended up coming up with a list of rules to when you should create a new content type.

New Content Types should be created when (any of the following apply):