Need to build a content model with related child records? Need to have your content entry/edit form UI's be intuitive and slick? Does "one to many" mean something to you when modeling your content types? Are you giving your content editors "user thought driven" interfaces?

With a small IA footprint and a handful of modules, you can now offer your content editors interfaces with extended visibility across all related content types and nodes within one single node entry/edit form.

Views takes care of displaying our new parent/child displays with ease.

p.s. not a single taxonomy vocabulary or term in sight with this approach :)