![]() ![]() This means we need that antiquated Content Type Hub to be able to syndicate our information architecture across Site Collections. In most organizations – as part of the move to modern and to take advntage of new innovations like Hub Sites – we’re working to flatten those old topologies. Now that we are moving to a flatter site topology, the Content Type Hub is really important. ![]() There are many different types of SharePoint implementations, and I get to see a lot of them, there is no one-size-fits-all thinking here. If you work with or in a large organization, you may say no one would be using SharePoint this way – and you’d be wrong. But in many cases, the Content Type Hub wasn’t needed, as there were few Content Types shared across Site Collections or there were too few Site Collections to drive its use. If we needed wider coverage of the information architecture (more than one Site Collection) we used the Content Type Hub to manage Content Types which we needed to use across Site Collections. ![]() When this was the case, we could set up Content Types in the root site in the Site Collection, then every subsite could use those Content Types and Site Columns easily because of the inheritance model. Many smaller organizations – and even some large ones – only used one Site Collection for most things in SharePoint. (And by the time we get there, the promised land will have moved on another few hundred miles.) Chasm One – Managing Content Types There are challenges here, and we have several chasms to cross before we’re in the promised land. To me, it feels like we’re nearing the end of one of the cycles, as modern SharePoint has almost fully taken hold – at least in Office 365. Rather than waiting for three year product cycles like we did in the past, we’re along for the ride. We’re in an interesting time in the SharePoint world. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |