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.
This is what we often hear as requirements from our customers:
> Tree navigation where tree structure can be easily edited (drag & drop and/or copy/move actions in the tree)
> TOC built from headings on the page
> adding images using clipboard
Adrian Fiechter commented
An easy editable and tree based navigation for a lot of pages
The ability to easily see the changes in the page compared to previous versions. Like in the classic pages.
Ability to force a accessibility check before posting.
Look at Atlassian Confluence. Do that. Job done :)
Ability to print pages would be great. Currently printing sp pages is a pain point for some of our users.
Floridian Wobee commented
We don't need or want linking syntax. We could use a link UI on the ribbon that links to other pages.
It would be great if there was a page library type that was designed as a KB, that assumes that we want to link pages together and have an outline structure of pages in a hierarchy.
I'm in the process of migrating wiki pages from a non-SPO site to a SPO Communication site as modern pages.
-Please include the ability of adding already created modern pages to a new wiki (or a built in way to convert them into "wiki" pages).
I'd hate to have to migrate 100's of pages all over again.
Christine Green commented
We remove the wiki tab from Teams and use OneNote instead. I don't understand why the wiki tab is there, as the functionality is so limited right now.
Jake Mannion commented
1. Copy/Paste support for images from the clipboard
3. Wiki linking syntax []
4. Ability to categorize wiki pages
5. Page comments and ratings
6. Page template support
We need a TOC based on Heading formatting (H1,H2,H3, etc.) I can't believe you didn't mention this in your comment, it's an incredibly common ask.
We need to be able to turn OFF wikis for Teams. Team Owners should be able to disable this. This ensures people use the right wikis.
I'm sure I'll have more comments if I think about this for more than two seconds.
Really great to hear. We've managed to utilize almost all the new features of modern pages to migrate our confluence wiki knowledge base (metadata, new webparts, templates, all great). Our biggest ask right now is that the text webpart support the clipboard for copy and paste of images. Currently this functionaly breaks up the text webpart by inserting an image webpart, which would be fine except for situations where were need inline images in ordered and unordered lists. These lists are a very common content element in Wiki's. As a stopgap, we've rolled our own TinyMCE editor to support this in the SPFx modern page environment, but I'm worried this is going to be an issue down the road.
S 4 commented
I asked Bill Baer about this at the Collab Summit conference last year. He said it was on the roadmap, seeing as theres been no update from MS on this here sounds like it never was.
Wiki pages are at the core of SharePoint functionality and yet have never been enhanced since MOSS days. Microsoft please spend less time on countdown timers and Teams webparts and focus on core functionality that employees need!
Rachel Riggin commented
Does anyone remember the short-lived "information" site -- or something like that? A few years ago, I seem to recall hearing about a new site template that would be perfect for wiki or knowledge base-type content. But the whole thing got scrapped. I was so excited and it just vanished. :-(
Without an ability to create an index page ideally based on tags to have similar pages grouped, or a auto TOC and better inline handling of images, MS should be embarassed to say sharepoint wiki is an enterpeise wiki.
Ali Salih commented
This is an absolutely must. Especially given that MS Teams Wiki solution is quite deficient as well, an SPFx-based Wiki solution that would work in both SPO and MS Teams would rock!
I've never been able to champion SharePoint's wiki features because they are so lacking. MSFT finally added a markdown webpart with little fanfare. Even a TOC would be helpful now, but really, a full revamp is long overdue.
Teams has made wiki support both more in-demand (because users see it and get excited) but simultaneously less supported (because there is a wiki/channel and far fewer features than SharePoint's enterprise wiki).
This should be simple. Just like how there's a communication site, there should be a wiki site. it's landing page introduces categories, maybe a word cloud, recent activity, an intro blurb and graphics, spotlight article, etc. The rest of it is just a page library with ratings, categories, responsive design, etc.
Nothing revolutionary, but tried and true and still missing for god knows what reason.
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!