Drupal Pattern: When to use different content types

As a general rule of thumb, any content which requires one of the following, is a candidate for its own content type:

  • discrete fields, not used often or at all in other pieces of content
  • business logic unique to the piece of content ( access requirements, section placement, workflow)
  • major layout or page structure differences in the presentation layer
  • different uses or discrete conceptual differences ( a blog page and a page content type may be excactly the same, be tagged the same, but require content contributors to think of them and their uses differently)
  • list separation requirements such as: a block of just Company news and a block of just department News

Now there are always exceptions and other ways to meet the same functional requirements. The last item above, for example, would likely be best met via taxonomy. Others functionality may be developed using context. 

Share or Comment via Twitter