My dilemma is this. At the moment I have a content type called "equipment" that I want to have a taxonomy term that will give a type of equipment, based on the selected type I want a new "cluster" of fields and/or taxonomy terms to pop up.

There is likely a different/better way of organizing the data. Creating a new content type for each type of equipment doesn't seem very elegant, especially if I want to create a view for all of the equipment.

Any leads on where I can find a solution to this? My brain has problems with decorator patterns in SQL as well.

  • If "elegant" is important factor, then there can't be objective answer to this question. Views shouldn't really be a problem.
    – Mołot
    Commented Jan 8, 2016 at 23:20
  • It's not that important to me. I am basically asking if there is any kind of standard for this. As someone who is not yet working in software, I want to understand "best practices" when they are available. Thanks!
    – Evan
    Commented Jan 8, 2016 at 23:29
  • See drupal.stackexchange.com/q/78364/16495
    – Mołot
    Commented Jan 8, 2016 at 23:32

1 Answer 1


Probably the easiest solution is to have a single content type, add all fields that you need in any possible situation, and use Conditional Fields to hide/show fields based on the chosen equipment type taxonomy term.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.