In content strategy choices upgrading from KX13 I often struggle with the choice where to put the data when a true parent/child relation would be desired. In KX13 you would have a tree-node, with child nodes, but moving those to the contenthub would feel like a better place, because of reusability and not the need to have that content within a channel.
Especially in cases where a child would have no meaning on it's own, and you don't want to have ghost-records it would be nice if those child-records would be strictly bound to a parent:
Deleting the parent would also delete children
Child elements preferably cannot live on their own
Example:
EducationContent (containing info about the education)
EducationStartdateContent (containing info on startdate, and extra info for that date, like location etc.)
I know it is possible to prevent that EducationStartdateContent would be bound more than once, but what if EducationContent is deleted? It does not feel right to come up with a cleanup task, removing the ghost records afterwards, and there is no need to see the EducationStartdateContent in the contenthub itself, but only through it's parent.
Would it be an idea ContentItemSelector forcing parent child relationship, and to hide contentitems in the contenthub for which a parentid is set?
My question to the community: what are your solutions for this? Module classes? Use pages instead of reusable? Or something else?
Environment
- Xperience by Kentico version: [31.3.3].