I noticed a while back that you can’t select content types in the views in modern lists. It seems to be that users need to be able to create new list columns. At my first moment of thought, I find this actually a bad step backwards, as a good way of organizing your information architecture seems to be less important than ease of use. But then who are we serving? Developers or users?

Next to the missing content types this is also promoting list fields rather than site collection fields. But if we assume that we don’t need to reuse columns  then why would we want content types? This will absolutely be a nightmare if list columns with the same name have been created across 1000 sites and you want to use search to filter on the column values.

For lists not really too much of a problem. A content type could be seen as something that groups reusable fields. Or maybe a special kind of list column. Both are not really needed if we only use list columns. You could even create a column called content type if you really want to be able to group/filter/search content!

And that problem of searching could be resolved if you use templates to create the sites. I could imagine exporting and importing PnP templates and therefore create identical columns, just to keep those developers happy that need to create search based web parts.

So are Content Types  in SharePoint dead?

 

 

 

Advertisements