Forum Discussion
Solved
SharePoint Online - classic configuration or not?
We are implementing a greenfield modern SharePoint structure using a hub and team sites. It seems to me that functions like content types, workflows and to some extent the term store are slowly being...
- I think using the modern experience for green field scenarios should be your primary goal. Many of the structures / functions from classic experience are still there or have an equivalent that provides similar functionality. In general, deprecated functionality (once officially announced) will stay in SharePoint and supported by Microsoft for quite a long time.
I don't see any movement in the basic structures of Fields, Content Types, Taxonomy, Lists and Libraries. I think it's safe to build your solution around these for the foreseeable future.
There are many things in SharePoint Online still available that have a better, modern alternative. We shouldn't use these anymore in greenfield scenarios and we should plan to replace them in brownfield scenarios. For example I wouldn't design new solutions anymore that incorporate Workflow (2010/2013), InfoPath, BCS, Content Organizer, etc...
I think using the modern experience for green field scenarios should be your primary goal. Many of the structures / functions from classic experience are still there or have an equivalent that provides similar functionality. In general, deprecated functionality (once officially announced) will stay in SharePoint and supported by Microsoft for quite a long time.
I don't see any movement in the basic structures of Fields, Content Types, Taxonomy, Lists and Libraries. I think it's safe to build your solution around these for the foreseeable future.
There are many things in SharePoint Online still available that have a better, modern alternative. We shouldn't use these anymore in greenfield scenarios and we should plan to replace them in brownfield scenarios. For example I wouldn't design new solutions anymore that incorporate Workflow (2010/2013), InfoPath, BCS, Content Organizer, etc...
I don't see any movement in the basic structures of Fields, Content Types, Taxonomy, Lists and Libraries. I think it's safe to build your solution around these for the foreseeable future.
There are many things in SharePoint Online still available that have a better, modern alternative. We shouldn't use these anymore in greenfield scenarios and we should plan to replace them in brownfield scenarios. For example I wouldn't design new solutions anymore that incorporate Workflow (2010/2013), InfoPath, BCS, Content Organizer, etc...