How two content fragment models can be setup to manage parent-child kinds of relationship? Let's say I have an account model and a product model. An account can have multiple products. A product must be attached to an account. I want to create services that wrap around the two models to serve different apps.
It will be nice the content fragment model can support content fragment creations so that child fragments will be instantiated under parent fragment instances. With that, the customized exporters/services will traverse the content fragment nodes and build corresponding JSONs. Basically node structures will make CRUD ops easier.
I like approach 1. I suppose the associated content is established through a field called <Content Reference> from parent CF to child CF. Parent and child CFs can locate at the default locations or any folders under /content/dam/<project>
Approach 2 is more suitable for loosely coupled relationships in respect of CF locations, types ...
I think there is another option.
Approach 3: leverage CF locations under /content/dam/<project>/... Before creating a collection of child CFs, manually create a single:Folder that matches the parent CF name first(nice to automate this). Then create the collection under that folder.