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.
It seems the modern pages don't allow for easily creating a wiki library, and the old wiki web part looks out-of-date. We are about to create a new knowledge base on how to use SharePoint and O365.
Management wants to us to use the technology we are promoting (SharePoint) and not resort to ServiceNow or another tool. Yet the Wiki pages look so out-of-date and conversion to modern view isn't even on the roadmap. It looks like we will just go ahead and use the classic-look wiki webpart and have that as the face of SharePoint for our organisation. Not ideal.
copy paste images would already be a massive benefit..... or use OneNote
Make look like Technet or extend the Teams wiki that is also very useful. Also think about a location feature to show wiki articles all over the O365 landscape. Imagine what you can do with such a functionality!
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.