Enterprise wiki site collection template which work on the new experience (modern interface)

%3CLINGO-SUB%20id%3D%22lingo-sub-488574%22%20slang%3D%22en-US%22%3EEnterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-488574%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20each%20sharepoint%20project%20i%20worked%20on%20i%20always%20add%20an%20Enterprise%20wiki%20site%20collection%2C%20as%20it%20is%20a%20very%20powerful%20template%20to%20build%20an%20intranet%20knowledge%20base%20for%20our%20customers%2C%20as%20follow%3A-%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20789px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F110705i496D55110AE40A0F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%221352810.png%22%20title%3D%221352810.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20do%20these%20main%20steps%20on%20the%20enterprise%20wiki%20site%20collection%3A-%3C%2FP%3E%3CP%3E1)%20i%20add%20some%20metadata%20site%20columns%20to%20the%20enterprise%20wiki%20page%20layout%20and%20content%20type.%20so%20users%20can%20link%20the%20wiki%20page%20to%20multiple%20metadata%20columns%20(which%20are%20Type%2C%20Security%20%26amp%3B%20customer%20in%20my%20case).%3C%2FP%3E%3CP%3E2)%20using%20sharepoint%20designer%2C%20i%20define%20a%20cusotm%20page%20layout%20which%20contain%20these%20custom%20metadata%20columns.%20the%20wiki%20pages'%20page%20layout%20will%20be%20as%20follow%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fgetfile%2F1352816%22%20alt%3D%22%22%20border%3D%220%22%20%2F%3E%3C%2FP%3E%3CP%3E3)%20i%20enable%20the%20metadata%20navigation%20for%20the%20wiki%20page%20library%2C%20so%20users%20can%20filter%20and%20search%20the%20wiki%20pages%20using%20the%20metadata%20columns%2C%20as%20follow%3A-%3C%2FP%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fgetfile%2F1352817%22%20alt%3D%22%22%20border%3D%220%22%20%2F%3E%3C%2FP%3E%3CP%3EI%20did%20this%20inside%20sharepoint%20online%2C%20on-premises%202013%20%26amp%3B%20on-premises%202016.%20%3CSTRONG%3Ebut%20one%20drawback%20i%20am%20currently%20facing%20inside%20my%20sharepoint%20online%2C%20is%20that%20the%20Enterprise%20wiki%20site%20collection%20does%20not%20have%20Modern%2FNew%20experience%3C%2FSTRONG%3E.%20Where%20all%20the%20above%20features%20(providing%20custom%20page%20layout%2C%20enable%20metadata%20navigation%2Ffiltering%20and%20viewing%20the%20wiki%20page%20itself)%20which%20I%20have%20implemented%20will%20be%20rendered%20in%20the%20classic%20experience.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20can%20anyone%20advice%20on%20these%203%20questions%3A-%3C%2FP%3E%3CP%3E%3CSTRONG%3E1.%3C%2FSTRONG%3E%20Can%20we%20enable%20the%20New%2FModern%20experience%20for%20our%20Enterprise%20wiki%20site%20collection%20and%20its%20features%3F%20so%20i%20can%20view%2C%20edit%20%26amp%3B%20search%20the%20wiki%20pages%20using%20the%20New%2FModern%20experience%20%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3E2.%3C%2FSTRONG%3E%20If%20the%20answer%20to%20my%20first%20question%20is%20No.%20Then%20are%20there%20other%20templates%20which%20i%20can%20use%20to%20build%20a%20SharePoint%20online%20enterprise%20wiki%20site%20collection%20(with%20similar%20functionalists%20to%20my%20current%20site%20collections)%20which%20have%20modern%2FNew%20experience%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3E3.%3C%2FSTRONG%3E%20If%20the%20answer%20to%20my%20second%20question%20is%20No%2C%20then%20will%20choosing%20the%20classic%20Enterprise%20wiki%20site%20collection%20to%20create%20a%20new%20sharepoint%20online%20site%20a%20correct%20decision%20to%20take%3F%20or%20this%20template%20might%20be%20depreciated%20in%20the%20near%20future%3F%20or%20there%20is%20not%20any%20problem%20if%20we%20use%20this%20classic%20enterprise%20wiki%20template%2C%20to%20create%20a%20new%20SP%20online%20site%3F%3C%2FP%3E%3CP%3EThank%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-488574%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-489312%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-489312%22%20slang%3D%22en-US%22%3EYou%20can%20basically%20get%20this%20same%20outcome%20with%20a%20communication%20site.%20You%20can%20add%20your%20metadata%20to%20the%20Site%20Pages%20library%20and%20show%20the%20metadata%20on%20the%20page%20using%20the%20Page%20Properties%20web%20part.%20Furthermore%2C%20you%20can%20use%20Highlighted%20Content%20to%20connect%20pages%20together%20to%20show%20%E2%80%9Crelated%20pages%E2%80%9D%20by%20filtering%20on%20a%20page%20property.%20This%20will%20actually%20create%20a%20more%20engaging%20experience%20than%20the%20classic%20wiki%20page.%20You%20can%20create%20a%20navigational%20experience%20for%20the%20site%20using%20a%20view%20of%20the%20site%20pages%20library%20on%20the%20home%20page%20of%20the%20site%20and%20also%20add%20Highlighted%20Content%20to%20show%20pages%20targeted%20to%20the%20current%20user%20(coming%20soon)%20or%20trending%2Fpopular%20pages.%20Once%20you%20have%20a%20page%20layout%20you%20like%2C%20you%20can%20save%20it%20as%20a%20page%20template.%20This%20feature%20(page%20template)%20may%20not%20be%20in%20your%20tenant%20yet%20but%20it%20is%20rolling%20out%20now.%20I%20think%20you%20will%20find%20modern%20pages%20so%20much%20better%20than%20the%20classic%20wiki%20pages%20and%20they%20work%20on%20mobile%20too.%20Try%20this%20and%20let%20me%20know%20if%20you%20have%20questions.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-499794%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-499794%22%20slang%3D%22en-US%22%3E%40susanHanley%20is%20correct.%20And%20I've%20used%20her%20process%20on%20my%20O365%20User%20site.%20You%20do%20not%20need%20a%20new%20site%2C%20but%20you%20will%20need%20all%20new%20pages.%20Unfortunately%20you%20can't%20%22convert%22%20wiki%20pages%20to%20site%20pages.%20Here's%20my%20example%3A%3CBR%20%2F%3E%3CBR%20%2F%3EOn%20my%20User%20site%2C%20I%20have%20a%20site%20column%20for%20%22O365App%22%20so%20I%20can%20tag%20things%20as%20SharePoint%2C%20Teams%2C%20Planner%2C%20etc.%20Since%20my%20content%20is%20posted%20both%20as%20pages%20(tips%20%26amp%3B%20tricks%2C%20links%20to%20resources%2C%20MVP%20blog%20posts%2C%20Microsoft%20documentation)%20and%20as%20documents%20(mostly%20presentations%20from%20conferences%20I've%20attended)%2C%20I've%20added%20that%20column%20to%20both%20the%20site%20pages%20AND%20document%20libraries%20and%20tagged%20content%20appropriately.%20I%20have%20a%20page%20for%20each%20application%20and%20on%20each%20page%2C%20I%20have%20highlighted%20content%20web%20parts%20that%20shows%20all%20the%20content%20from%20my%20site%20that%20I've%20tagged%20for%20that%20application.%20Actually%2C%20I%20have%202%20web%20parts%20because%20I%20want%20to%20segregate%20out%20the%20conference%20presentations%20from%20the%20pages%2Fposts.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20now%20users%20can%20come%20to%20my%20site%20and%20choose%20how%20to%20find%20information.%20They%20can%20go%20to%20the%20SharePoint%20page%20or%20the%20Teams%20page%20or%20the%20Planner%20page%20and%20browse%20through%20all%20the%20stuff%20I've%20posted%20about%20that%20topic%20OR%20they%20can%20search%20for%20a%20topic.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-630324%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-630324%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F57004%22%20target%3D%22_blank%22%3E%40Rachel%20Davis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20the%20reply.%20but%20not%20sure%20what%20do%20you%20exactly%20mean%20by%20%22User%20site%22%3F%20are%20you%20talking%20about%20onedrive%20site%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-630888%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-630888%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOk%20thanks%20for%20the%20detailed%20reply.%20I%20think%20i%20will%20test%20your%20appraoch.%20as%20seems%20using%20the%20old%2Ftraditional%20enterprise%20wiki%20site%20collection%20will%20not%20have%20any%20future%20improvement.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633337%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633337%22%20slang%3D%22en-US%22%3ESorry%2C%20that's%20just%20our%20nickname%20for%20the%20site.%20The%20full%20name%20is%20%22O365%20Collaboration%20User%20Adoption%22%20site.%20We%20call%20it%20the%20User%20site%20for%20short.%20It's%20a%20modern%2C%20group-enabled%20Team%20site.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633377%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633377%22%20slang%3D%22en-US%22%3EWiki%20PAGES%20will%20not%20have%20any%20future%20improvement%2C%20but%20if%20you%20use%20MODERN%20pages%20-%20even%20on%20a%20traditional%20site%2C%20the%20vast%20majority%20of%20the%20new%20features%20will%20work.%20Certainly%20the%20things%20that%20Susan%20and%20I%20have%20mentioned%20will%20work.%20We%20have%20thousands%20of%20traditional%20sites%20and%20subsites.%20We%20are%20not%20migrating%20them%20to%20new%20Team%20or%20Communication%20sites.%20But%20we%20are%20modernizing%20them%20by%20using%20modern%20pages%2C%20etc.%3CBR%20%2F%3E%3CBR%20%2F%3EMigrating%20is%20a%20pain%20as%20it%20means%20directing%20users%20to%20a%20new%20URL%20and%20breaking%20any%20links%20or%20bookmarks%20that%20come%20to%20the%20existing%20site.%20I%20would%20just%20rebuild%20your%20existing%20site%20with%20modern%20pages.%20You%20can%20build%20the%20modern%20pages%20in%20the%20background%20and%20simply%20not%20put%20out%20the%20navigation%20link%20until%20you're%20ready.%20When%20you're%20ready%2C%20rename%20the%20existing%20home%20page%20%22home-OLD%22%2C%20then%20name%20your%20new%20modern%20page%20as%20home.aspx%20and%20set%20as%20the%20site%20home%20page.%20Voila!%3CBR%20%2F%3E%3CBR%20%2F%3EThen%2C%20when%20user%20goes%20to%20their%20existing%20bookmark%20for%20the%20home%20page%20to%20your%20site%2C%20it%20will%20still%20work.%20As%20will%20any%20links%20that%20other%20people%20have%20made%20to%20your%20site.%3CBR%20%2F%3E%3CBR%20%2F%3EYou'll%20have%20to%20decide%20how%20to%20handle%20all%20the%20old%20wiki%20pages%20and%20that%20may%20depend%20on%20how%20many%20there%20are.%20Maybe%20you%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633431%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633431%22%20slang%3D%22en-US%22%3EI%20would%20still%20recommend%20converting%20the%20site%20to%20a%20modern%20site%2C%20but%20it%20is%20a%20choice%2C%20as%20you%20suggest.%20My%20general%20feeling%20is%20that%20you%20want%20to%20bite%20the%20bullet%20and%20upgrade%20wherever%20possible.%20It%20may%20be%20painful%20for%20a%20short%20time%2C%20but%20I%20think%20it%20creates%20a%20more%20future-proof%20environment.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-634427%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-634427%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E%26nbsp%3B%26nbsp%3BI%20have%20yet%20to%20have%20anyone%20give%20me%20a%20good%20business%20justification%20for%20going%20through%20the%20pain%20and%20expense%20of%20migrating%20a%20classic%20site%20to%20a%20communication%20site.%20A%20group%20enabled%20Team%20site%20is%20one%20thing%2C%20but%20not%20a%20communication%20site.%20The%20functionality%20is%20almost%20identical%2C%20certainly%20for%20what%20this%20guy%20is%20asking%20about.%20I%20would%20argue%20that%20a%20classic%20site%20has%20MORE%20options%20for%20list%20types%20than%20a%20communication%20site%20which%20is%20limited%20to%20a%20custom%20list%20and%20an%20event%20list.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20have%20solid%20functional%20reasons%20for%20migrating%20my%20classic%20sites%20to%20a%20communication%20site%2C%20I'd%20love%20to%20hear%20them%20and%20take%20them%20back%20to%20my%20IT.%20But%20for%20now%2C%20if%20I%20can%20do%20all%20the%20things%20you%20talk%20about%20on%20my%20current%20site%20without%20the%20pain%20of%20migrating%2C%20why%20should%20I%20do%20it%20or%20put%20my%20users%20through%20that%20hassle%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-634463%22%20slang%3D%22en-US%22%3ERe%3A%20Enterprise%20wiki%20site%20collection%20template%20which%20work%20on%20the%20new%20experience%20(modern%20interface)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-634463%22%20slang%3D%22en-US%22%3EI%20think%20the%20best%20reason%20is%20future-proofing%20and%20not%20having%20a%20site%20that%20is%20half-classic%20and%20half-modern.%20And%20I'm%20seeing%20some%20training%20issues%20for%20site%20owners%20of%20these%20franken-sites.%20It's%20clear%20that%20net%20new%20sites%20should%20be%20modern.%20For%20legacy%20team%20sites%2C%20the%20answer%20is%20%22it%20depends.%22%3C%2FLINGO-BODY%3E
Highlighted
Valued Contributor

On each sharepoint project i worked on i always add an Enterprise wiki site collection, as it is a very powerful template to build an intranet knowledge base for our customers, as follow:-

1352810.png

I do these main steps on the enterprise wiki site collection:-

1) i add some metadata site columns to the enterprise wiki page layout and content type. so users can link the wiki page to multiple metadata columns (which are Type, Security & customer in my case).

2) using sharepoint designer, i define a cusotm page layout which contain these custom metadata columns. the wiki pages' page layout will be as follow:-

 

3) i enable the metadata navigation for the wiki page library, so users can filter and search the wiki pages using the metadata columns, as follow:-

I did this inside sharepoint online, on-premises 2013 & on-premises 2016. but one drawback i am currently facing inside my sharepoint online, is that the Enterprise wiki site collection does not have Modern/New experience. Where all the above features (providing custom page layout, enable metadata navigation/filtering and viewing the wiki page itself) which I have implemented will be rendered in the classic experience.

 

So can anyone advice on these 3 questions:-

1. Can we enable the New/Modern experience for our Enterprise wiki site collection and its features? so i can view, edit & search the wiki pages using the New/Modern experience ?

2. If the answer to my first question is No. Then are there other templates which i can use to build a SharePoint online enterprise wiki site collection (with similar functionalists to my current site collections) which have modern/New experience?

3. If the answer to my second question is No, then will choosing the classic Enterprise wiki site collection to create a new sharepoint online site a correct decision to take? or this template might be depreciated in the near future? or there is not any problem if we use this classic enterprise wiki template, to create a new SP online site?

Thank

9 Replies
Highlighted
You can basically get this same outcome with a communication site. You can add your metadata to the Site Pages library and show the metadata on the page using the Page Properties web part. Furthermore, you can use Highlighted Content to connect pages together to show “related pages” by filtering on a page property. This will actually create a more engaging experience than the classic wiki page. You can create a navigational experience for the site using a view of the site pages library on the home page of the site and also add Highlighted Content to show pages targeted to the current user (coming soon) or trending/popular pages. Once you have a page layout you like, you can save it as a page template. This feature (page template) may not be in your tenant yet but it is rolling out now. I think you will find modern pages so much better than the classic wiki pages and they work on mobile too. Try this and let me know if you have questions.
Highlighted
@susanHanley is correct. And I've used her process on my O365 User site. You do not need a new site, but you will need all new pages. Unfortunately you can't "convert" wiki pages to site pages. Here's my example:

On my User site, I have a site column for "O365App" so I can tag things as SharePoint, Teams, Planner, etc. Since my content is posted both as pages (tips & tricks, links to resources, MVP blog posts, Microsoft documentation) and as documents (mostly presentations from conferences I've attended), I've added that column to both the site pages AND document libraries and tagged content appropriately. I have a page for each application and on each page, I have highlighted content web parts that shows all the content from my site that I've tagged for that application. Actually, I have 2 web parts because I want to segregate out the conference presentations from the pages/posts.

So now users can come to my site and choose how to find information. They can go to the SharePoint page or the Teams page or the Planner page and browse through all the stuff I've posted about that topic OR they can search for a topic.
Highlighted

@Rachel Davis 

thanks for the reply. but not sure what do you exactly mean by "User site"? are you talking about onedrive site?

@Susan Hanley 

Ok thanks for the detailed reply. I think i will test your appraoch. as seems using the old/traditional enterprise wiki site collection will not have any future improvement.

Highlighted
Sorry, that's just our nickname for the site. The full name is "O365 Collaboration User Adoption" site. We call it the User site for short. It's a modern, group-enabled Team site.
Highlighted
Wiki PAGES will not have any future improvement, but if you use MODERN pages - even on a traditional site, the vast majority of the new features will work. Certainly the things that Susan and I have mentioned will work. We have thousands of traditional sites and subsites. We are not migrating them to new Team or Communication sites. But we are modernizing them by using modern pages, etc.

Migrating is a pain as it means directing users to a new URL and breaking any links or bookmarks that come to the existing site. I would just rebuild your existing site with modern pages. You can build the modern pages in the background and simply not put out the navigation link until you're ready. When you're ready, rename the existing home page "home-OLD", then name your new modern page as home.aspx and set as the site home page. Voila!

Then, when user goes to their existing bookmark for the home page to your site, it will still work. As will any links that other people have made to your site.

You'll have to decide how to handle all the old wiki pages and that may depend on how many there are. Maybe you
Highlighted
I would still recommend converting the site to a modern site, but it is a choice, as you suggest. My general feeling is that you want to bite the bullet and upgrade wherever possible. It may be painful for a short time, but I think it creates a more future-proof environment.
Highlighted

@Susan Hanley  I have yet to have anyone give me a good business justification for going through the pain and expense of migrating a classic site to a communication site. A group enabled Team site is one thing, but not a communication site. The functionality is almost identical, certainly for what this guy is asking about. I would argue that a classic site has MORE options for list types than a communication site which is limited to a custom list and an event list.

 

If you have solid functional reasons for migrating my classic sites to a communication site, I'd love to hear them and take them back to my IT. But for now, if I can do all the things you talk about on my current site without the pain of migrating, why should I do it or put my users through that hassle?

Highlighted
I think the best reason is future-proofing and not having a site that is half-classic and half-modern. And I'm seeing some training issues for site owners of these franken-sites. It's clear that net new sites should be modern. For legacy team sites, the answer is "it depends."