Subclassing content type forms I was wondering how would you guys approach a situation where your Drupal7 site required a couple of custom content type, yet most of the fields would be shared across them. What I mean resembles a typical object-oriented case of a super class and its subclasses.

I want it so that I can make the admin-side content filling easier for the owner of the site. I also assume that for me, as the author of the form it would be a great time-saver if I could base one on another.

Is it possible? Does it make sense? Or would you rather make one type with all possible fields merged onto one form, then tweak the suggestion template so that irrelevant parts are /shown/hidden upon changing a dropdown menu that specifies the subclass?

Anyone been through a similar problem?
Or would you rather make one type with all possible fields merged onto
  one form, then tweak the suggestion template so that irrelevant parts
  are /shown/hidden upon changing a dropdown menu that specifies the
  subclass?


If you're going the single-type route, here are two tips: Drupal Forms API supports conditions, check the docs; it might be useful to take a look at the Prepopulate module.