Feb 27 2019 09:04 AM
Feb 27 2019 10:40 AM
I haven't seen communication of what'll happen with SharePoint wiki pages, but, is there something about specific to a Wiki page that can't be accomplished by a Modern site page?
Feb 27 2019 10:43 AM
Jun 06 2019 02:34 AM
Found this recent reply from Microsoft on their SharePoint UserVoice page:
We know wikis are critical to sharing knowledge within your organization! We’ve been slowly building capabilities to share information more easily with our focus on modern pages and web parts. And with that work, we’ve been adding some of the capabilities we hear you want when people refer to wikis (easily add links to other pages or content, add metadata to each page to help people find and categorize it, roll-up content based on that metadata to show groupings of like content, etc.) But we know this isn’t all that’s required to have a great wiki. Many people also want wiki linking syntax e.g. [], we don’t yet support that, but we do support ctrl/command + K from the text web part to search and find pages on your site. We’ll be working on adding wiki syntax shortly. We know you also need easy roll-up pages, maybe an index page, etc.
In short, we’re still working on what it will take to make a great wiki experience leveraging the building blocks of web parts and modern pages. If you have specific ideas about what you need/want, we’d love to hear them. Please add detailed comments to help us frame what you need for our MVP.
So sounds like the wiki functionality might be replaced by better modern pages and web parts.
Nov 18 2021 02:05 PM - edited Nov 18 2021 02:06 PM
Until there is an "easy" button for building out Modern SharePoint Wiki's, I found this video for creating "a" modern SharePoint Wiki: https://www.youtube.com/watch?v=YWBGX4qc_mU&t=69s. Essentially building pages linked to each other and creating the breadcrumbs with a series of hyperlinks and text webpart. Seems like a lot of work, but for site designers--may be fun!
Jan 21 2022 05:33 AM
This is not ideal. We need what every other Wiki does. A simple tree structure navigation. It should be as simple as having a 'top parent page' field on every page. Then, have a setting in the page library to show a tree index, built from this information.
Right now, creating this is a nightmare, because you have to build the navigation alongside the content!
Jan 21 2022 06:22 AM
@XabiBeltza You can easily do this by creating metadata exactly as you describe. You could use a "lookup" field to connect pages to their logical parent and/or you can create a Topic column to connect similar pages together. You can then use the Highlighted Content web part to pull all related pages together. If you want pages to sort in a particular order - or at least easily identify the "parent" in each "family," you can add a number to the parent page title - e.g. 01-Name of Page. To connect pages to one another in line, you can use standard wiki notation [[ ]].
Jan 21 2022 07:00 AM
Totally agree. Just sharing a very detailed and an alternate way of creating a Modern Wiki Library experience for end-users I found beneficial. For any step of the tutorial, solutions can be altered...or eliminated to fit whatever use-case is required. I find it fun to implement the given alternative...but hey...that's me.
Jan 21 2022 08:05 AM
Feb 01 2022 04:26 PM - edited Feb 01 2022 04:28 PM
@Osman Beyaztas We've been able to get pretty close. We needed to move a lot of content from Confluence so we created a nav part via SpFX and setup our structure using managed metadata. We created templates with the appropriate metadata webparts as well as a TOC web part. We are extending visibility with Viva Topics consuming these pages and documents.