Apr 26 2019 07:46 PM - edited Apr 26 2019 07:54 PM
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:-
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
Apr 27 2019 05:38 AM
Apr 29 2019 08:00 AM
May 21 2019 03:58 PM
thanks for the reply. but not sure what do you exactly mean by "User site"? are you talking about onedrive site?
May 21 2019 04:02 PM
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.
May 22 2019 06:43 AM
May 22 2019 06:53 AM
May 22 2019 07:04 AM
May 22 2019 11:35 AM
@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?
May 22 2019 11:49 AM
Aug 23 2021 02:07 PM