(Content type) Compositions multiple level inheritance

[Luuk1983]

I just wrote about how I think the access rights system of Umbraco is too limited (#18018) and I called it 'one of the major weaknesses of Umbraco'. I want to address another weakness (imho) in this discussion: the lack of composition inheritance.

Currently when an element type is used as a composition, it cannot be used for anything else anymore. Once again comparing it to Sitecore, consider this scenario I would do in Sitecore all the time:

Have the following compostions:

• Hero (some fields for a page hero)
• SEO (description, sitemap and stuff like that)

In Sitecore I would create a composition like 'Content page base' that would inherit from compositions 'hero' and 'seo'. My 'Content page base' would be the composition that every page would inherit from. The upside is that if in the future I have a new composition that needed to be added to every content page, I could simply add it to the 'Content page base' composition and it would be available on all pages.

With multiple level inheritance of compositions, you can really create good reusable content types. Can I live with it. Sure I can, but in my day to day development life I come across situations like I described above where I would have like to have solved it differently for better maintainability.