Content Type Management Across Multitenant Sites

[fmontes]

Description

This feature aims to provide a more streamlined and intuitive approach to handling content types specific to each site, alongside the existing system content types that are shared across all sites.

• Allow users to create and manage content types for individual sites for a more organized content management structure.
• Allow users to copy content types when duplicating a site, ensuring that the new site inherits the content structure of the original.
• Filter content types by site within the content type portlet
• Generate a detailed report when deleting a site, showing the content types and number of items for each type. The report will offer choices to move this content to another site, preventing accidental data loss.

Infrastructure Modifications

• Modifications to the content type API to accept site identifiers.
• Updates to the user interface to support filtering by site while including system host content types.
• Leverage the existing metadata field within content types to store site identifiers, facilitating the association of content types with specific sites.
• Update the content types rest endpoints to support filtering by site.

### Tasks
- [ ] https://github.com/dotCMS/core/issues/27731
- [ ] https://github.com/dotCMS/core/issues/27755
- [ ] https://github.com/dotCMS/core/issues/28035
- [ ] https://github.com/dotCMS/core/issues/27732

[john-thomas-dotcms]

Some use cases to consider:

• User with 100 sites, wants one content type to be available to only 5 of those sites.
  • Is there a way to specify a content type for multiple sites, or is the only choice here to make 5 copies, or to make it global?
• User wants to promote a content type from a single-site content type to a global content type.
• User wants to demote a global content type to be available on only a single site.
• User wants to copy a single-site content type to another already-existing site (i.e., not during a site copy).
• User wants a content type (either global or site-specific) to be accessible by only certain roles.
  • IOW, how will permissions interact with the site-specificity?

I'm not familiar enough with the effort to have opinions on the best answers to any of these. But it's highly likely we'll get requests for most or all of these use cases from customers.