IA Value | Packaging and templatizing SharePoint sites, content, and structure

Hi,

I would like to see more details around content types architecture and best practices. I never saw a real business case example.

I consider Content Types as an important IA component.  

Things that I would like to see:

Usage

• Content Type only versus a mix of content type with a "document type" attribute (managed metadata)
  • When analyzing business types of content you could and up with 50,  100 content types. Should you regroup the types of content that share the same metadata by creating one content type for it and add a "Document Type" managed metadata to narrow down the type of content?
  • Content type requires more configuration as you need to create/deploy to sites then attach to library etc. compared to a document type attribute that you just need to add a new document type to your terms set.
• What is the futur of content type other than providing a structure of metadata now that workflow and policies/retention (and templates with the new document modern UI) are now decoupled from content types? Will there be impact on how we are using content types for automatic classification based on artifical intelligence? What are the guidelines?

Provisioning

• Site scripts are not an easy way to deploy site columns and content types. Writing json or using PowerShell is not for everyone where content type hub is more suitable.
• Content Type hub should be more stable and provide new features (Not just UI enhancements) like targeted sites publishing or publishing site columns only. What is coming regarding the content type hub?

Support

We assist in some changes or unsupported features that where available in classic UI

• Show/Hide content type at the folder level (Change new button order) to ease/limit content type selection for end users (This feature is not available anymore in modern UI... Why?)
• The "new" library menu: This is a nice feature where we can attach templates to content types. However these templates lives in the library forms folder. This is almost unpossible to update the templates if the content type and template are used in multiples libraries/sites. Also this is unaligned with the new Organizational Assets feature where we can store templates made available in Office.

Thanks!