Questions
Child article asset behavior in Flex
I just noticed this today, but it seems like child article assets attached to another asset behave the way we used to expect sibling assets to behave in the old Zen templates.
Complicated words. Let me explain.
For example, if you add an article as a child to another, it appears in the parent article's sidebar as a content box. However, if you then visit the "child" asset, it shows a similar content box that contains the "parent."
This reciprocal linking is the same way things work when articles are related as siblings; however, the sibling display is a simple list of headline links with no rich media.
Back under Zen templates, the reciprocal links would only happen when things were related as siblings. A child/parent relationship added the child as a sidebar to the parent.
It seems like the sibling and child relationships do exactly the same things under Flex, just with different formatting. Is this by design?
Shouldn't the parent/child relationship be more of a "this asset is subordinate to this other asset" relationship, rather than "these assets are on an equal footing"?
Customer support service by UserEcho
Example:
http://www.bozemandailychronicle.com/news/politics/montana-campaign-contribution-limits-to-rise-for-some-candidates/article_be96faff-ebca-51b3-9e54-0efff17ebc9a.html
http://www.bozemandailychronicle.com/news/politics/sandefur-reports-strong-fourth-quarter-fundraising-in-montana-supreme-court/article_ed11e39c-90a7-56cb-8215-7e226927d233.html
One of these is the parent. One is the child. Without using your browser's inspector to look at the classes, tell me which one's which. ;)
That's the argument I've been trying to make too, but less eloquently. There seems to be a lot of confusion as what is (and can be) a child or a sibling. YouTube assets and link assets, for example, cannot be sibling assets. But there are times when the logic says they're siblings, not children, of the article asset to which they're attached. It's maddening.