Say a part has a list of child "Interesting Facts" parts. I know how to create a N:N relationship between the two.
What i'm looking for though is a more user friendly way of letting users enter these InterestingFacts. They should be able to go into the parent content item and then add an arbitrary list of interestingFacts, and then save the part and have all the InterestingFact
items save into the InterestingFacts table, with a parent child relationship to the parent content item.
Like I said, database wise and Model wise I know how to make a part have a list of other parts (following the N:N example from the docs). What I'm looking for is a little guidance on making the UI sleeker, so the user can create the child parts at the same
time as editing the parent part.