A Total Revamp for Wikis
Could we please have the ability to create Wikis in SharePoint that look like TechNet or Wikipedia? Please try to make things more simple. Do not over complicate it again.
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.
Vince Jennings commented
page categorisation is very lacking in the SharePoint wiki, can something be done about this also?
I hope, that wiki will be also nice like others new document libraries.
Garrett H commented
I want the docs layout for the sharepoint wiki. It's so clean and it is organized well. I am literally trying to recreate it by hand. Just make this a thing.
Elissa Klotz commented
The SharePoint Wiki is more of web publishing platform than an actual wiki. I would like to see more web publishing pieces added. A traditional wiki is not needed, but a configurable cookie cutter UI that allows users to pick the design of the site or subsites.... Choices like MediaWiki, WordPress, Ektron, etc would really allow users to manage the sites as per their media needs.
Debanshu Debroy commented
Sharepoint needs to think about how its customers can migrate what they built on classic site to modern site. Organizations spent lot of effort to build wiki sites in classic site. We can't expect them to redo the whole effort to migrate to Modern site.
Adrian Goneau commented
We are using classic enterprise wikis for a large documentation site with a ton of custom navigation. There is no path to "modern" for us. Please give us some way to convert these pages to modern pages and a way to create complex navigation.
Bruce Hankins commented
Why not implement Markdown while you're at it
chris jefferies commented
The wiki setup is lame...
Yes, Microsoft Document pages were the ideal wiki for SharePoint :-)
Microsoft Documentation pages are our ideal format for a new wiki. If this format existed in Modern Pages, we'd be using it extensively. https://docs.microsoft.com/en-us/sharepoint/dev/features/hub-site/hub-site-overview
O365's current wiki works basically like a less functional version of One Notes.
see mediawiki.org for how a wiki should work.
use mediawiki's as inspiration for
Rapid TOC and page creation.
Improve on Mediawiki by...
Adding drag and drop for files in the active page .
Copy and pasting images in to page content flow.
Allowing for more text formatting options.
Improve wiki user permissions.
Microsoft. Enough Said.
Roy F commented
I just tried to create and use Sharepoint wiki pages todayand I quickly hit the lack of support for a page TOC and linking to content in other pages. Wow! I will have to kep my wiki pages in Confluence and link to those pages from our O365 content. Perhaps in a year things will be better.
I'm a CTO investigating SharePoint for our enterprise. I have a team that updates our public website hosted on WordPress, a team that writes our web-based software products in C#.NET/MVC, and our entire IT team uses Atlassian Confluence and Jira in conjunction with TFS. So, we're not Microsoft haters by any means.
Imagine my disappointment when I looked at Office 365 SharePoint for the non-IT staff and found that Confluence - a product that costs $10/month for up to 10 users! - runs circles around MS Sharepoint's Wiki. No only the Wiki, but the entire SharePoint product is embarassingly poor and subpar for Microsoft. Unfortunately, it doesn't even stop there. The whole of the O365 suite (Teams, Skype, Planner, and related apps appear to be a hodge-podge of poorly integrated applications. Microsoft, what happened?
It would be nice to know if this is going to end up on the roadmap or not. We are in the process of retiring Confluence, and we were considering using SharePoint as a replacement. The current Wiki feature is far too antiquated for us to even consider using it though, especially since everything else in our sites is leveraging the modern architecture. We are unwilling to implement something that would provide a very inconsistent experience for our end-users.
Why is this not the roadmap yet?
Can't believe this hasn't been done yet. The current SharePoint wiki is dreadful... This is forcing us to turn to alternative solutions like Confluence.
Hope Microsoft really can do somethings to enhance on the Wiki site user experience.
Ben Christian commented
It needs to be similar to confluence. We've tried to encourage users to use SharePoint sites for this purpose but they're going off and signing up for Confluence instead.
We need support for Markdown to be able to migrate from an old Wiki product that we're currently running internally.