11-10-2016 12:38 PM
11-10-2016 12:38 PM
We have done extensive work creating organized team sites (think information architecture) for our organization in classic sharepoint
As we look as starting to create Groups for various departments, projects, etc that have existing SharePoint sites, do you recommend doing mini-migrations to new Group sites and shutting down old SharePoint sites?
I'd prefer to have the ability to turn of SharePoint Sites on certain groups, but in lieu of that I also don't want sites all over the place not being used. Seems like an organization and duplication nightmare in some cases.
Example, a site collection called /sites/projects/ where each subsite is a specific project.
11-10-2016 12:44 PM
11-10-2016 12:45 PM
Brent. So the first answer - duplicates are bad, especially because search will find them!
I would be curious how you do you currently do global navigation. You bring up a good point that one of the issues with groups is that they're independent site collections and not in your direct navigation. However, for example, you could use managed metadata navigation to manual control where the departments link to.
One major consideration for moving departments to groups is the associated e-mail address. I would recommend transforming the distributation list to the group (because otherwise naming becomes a nightmare.
Remember that a group team site (weird name but you know what I mean) is a full site collection so if you have the department = group you can still have /sites/group/subsite.
In short, MOVE the content!
11-10-2016 12:47 PM
The team is wokring on plans to enable various capabilities to "groupify" classic team sites. The team is looking at a phased approach and we'll have more to share soon.
To date, in production, classic sites have received modern document libraries, modern lists, modern site contents page, ability to create modrn publishing pages - and you can create a modern page and declare it as your home page (on the classic site). More to come per the modernization effort, with the want to be able to connect the classic team site to a Office 365 group...
In all, I'd not suggest mifgration, but a little patience and focus today on using the modern components within classic sites, and then groupifying them when you can per the method(s) we'll enable.
11-10-2016 12:51 PM
11-11-2016 06:13 AM
@Adam Levithan to answer your question, we did a custom drop down mega menu that we inject into our site collections using usercustomactions. It is a html/css based menu that we load from a centralized location (update once and it automatically updates everywhere in SharePoint).
Site-level Global Navigation is too limited, Managed Metadata Navigation never worked well especially across site collections. There is no true "organizationally enforced" menu that can be shown on all SharePoint sites. The current model is moving to a "bucket of unorganized sites that you have a access to" that you can just get to from the SharePoint home. But we have hundreds upon hundreds of sites, and we need to make sure that the top 10-20 fully endorsed ones are easily discoverable and accessible by all of our users.
<jumping off of soapbox>
We do a little bit of branding to go along with it, but what it gives us is at the top of EVERY page in our SharePoint environment a quick menu that will take you to:
05-02-2017 07:47 PM
Any updates on group-a-fying classic sites. Our timeline has us migrating some larger departments soon and I am very worried about the classic site vs 0365 group connected sites. I am loving the modern sites and all the integration. Should we "hold" the migration to the already created classic sites with global nav and customization or move forward and hope for full 0365 group integration soon.
Thanks in advance.
05-03-2017 11:17 AM
by John Wynne on August 30, 2018
by Hemant Mane on August 30, 2018
by Cathy Dew on May 21, 2020
by DC Padur on May 18, 2020
by SPDev_Support on May 06, 2020