Looking for a way to store sub-assets under a CF or apply a clear hierarchy to how CFs are stored. The sub-assets would always be unique to the parent asset and not always required. The sub CF and parent CF would also require different models, so variations aren't a good solution.
Based on the data hierarchy, it would be much easier for authors to view sub-assets tied to the parent asset as opposed to simply using reference fields. Ideally, this would be similar to how pages are structured within the sites console. Example:
- Whole data object 1
- Component a
- Component b
- Component c
- Whole data object 2
- Whole data object 3