There are cases, such as with silverstripe/taxonomy, where related classes should be managed in different ways.
In the case of siverstripe/taxonomy, the TaxonomyTerm class should be managed as a tree, but TaxonomyType should be managed in a gridfield. But they should be in a shared admin section.
After https://github.com/silverstripe/silverstripe-cms/issues/2951 is done, we'll be able to manage any arbitrary hierarchical model class in a tree structure - but each model class must have its own admin section.
There are cases, such as with
silverstripe/taxonomy, where related classes should be managed in different ways. In the case ofsiverstripe/taxonomy, theTaxonomyTermclass should be managed as a tree, butTaxonomyTypeshould be managed in a gridfield. But they should be in a shared admin section.Related
Acceptance criteria
ModelAdmincan declare that a given tab or tabs should be managed as a treeModelAdminsubclasses can have different models in different tabs, some as trees and some as gridfieldsTaxonomyTermclass is managed as a tree view