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.
Adriaan Van Nuffel commented
We need a table of contents, based on the text headings.
Also, editing a Modern page in Sharepoint is still complicated for some users. A functionality closer to the Wiki pages in MS Teams would be great. (Just write text and paste images, not bothering with web parts).
I also like the layout in MS Teams, sober yet attractive.
And like Jaymz wrote below: docs.microsoft.com is a great layout too, if we could make this in Sharepoint, that would be nice. (A main navigation to the left, and an in-page navigation based on the headers, on the right)
Jared Pittman commented
currently using modern site w/ custom field for managed metadata tagging, and template pages that guide our authors on all of the custom things that they have to remember to do in order for their page to come out right. Would be much better if this was simplified, related articles easy to tag, managed metadata clickable so that anything tagged comes up in search, etc...
Also really miss [] syntax
+1 Wiki linking syntax [] or some type of linking method
+1 Templates for standard formatting/styles and structure
Honestly, what you have in docs.microsoft.com is perfect. Mirror that in SPFx
I know MS you are working hard to listen what people want and get your job done. As name suggested SharePoint should be shared documents, and knowledge among teams, and wiki / knowledge base is extremely important. Using classic wiki app in a modern site is not practical, not only dead old view, but also lack of features.
I see all previous admin replies that you were thinking about it for more than 3 years, I think it's been long enough to listen and think, and it's time to get it done.
Having a separate wiki outside of Office 365 is nonsense, but that's how most of people do currently.
Thanks for reading my ignorant comment, and I appreciate your hard work.
Aman Arora commented
This will be extremely helpful. Adding the feature of creating internal knowledge base/wikis easily is something that will increase the adoption of Sharepoint a lot. This is one feature that is lacking in Office 365 for which we have to resort to Atlassian Confluence.
1. Create page with standard templates (and user creatable templates)
2. Good text/content editing capabilities (adding hyperlinks, images, section headers, etc)
3. Navigation bar on the left that automatically updates and is hierarchical.
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.
SharePoint Admin in the South 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. :-(