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.
Nikolai Kalliola commented
Currently trying to build a wiki page from existing Word documents. The goal is to quit using the files and use the site pages instead. The documents however use specific numbering and I am unable to do this in SharePoint Modern. Please, this is a severely needed feature!
No updates since 2019!!! Should we be looking at something other than SharePoint for knowledge management?
Jose Nava commented
Any updates yet?
MS Admin - can you please provide progress here? Almost 2 years since we see it in Thinking mode. As such this idea is ongoing with you for 5 years now.
Fredrik Work commented
Cant help to wonder why this takes serveral years to develop... I mean modern pages looks like its in beta since it was launched.
Paul Serghe commented
It would also be really nice to have some advanced style features similar to Site Pages and Word documents. Currently the wiki library styles and formatting options are very limited.
Jason Kirk commented
This has been going on for a while and still nothing. I really like the wiki experience in Teams, at least as a starting place. I also got excited when I saw the customlearningadmin.aspx page in the Learning Pathways, but there is no way to leverage that for use in other sites.
Right now we are embedding a OneNote notebook into a SharePoint modern page as I am hoping a solution will come out soon. I don't to build something if something is coming out soon.
Yes, the current wiki experience is very old and dated and adds nothing to the UX. A wiki section should have several key features, such as pagination, wiki navigation etc.
Could you provide an update to this? I don't see any updates and noticed a support article was briefly posted about a new Table of Contents web part and then removed.
I used the pages to make a wiki (knowledge base), but 2 essential features are missing
while waiting for the development of a professional wiki, by you hoping quickly :o). we need two small modifications:
1- To be able to make an automatic summary of the pages.
2- the metadata of the pages be clickable (in webpart : Properties of the page).
I remain at your disposal if you wish to discuss this subject, I have lots of idea
Jim Tolson commented
My guess is that once Project Cortex's Knowledge Center and Topic Pages/Topic cards are released that SharePoint Wiki's will be dead?
Can we get an update on this user voice post to confirm?
Can we please have our annual progress update from MS on this?
I used this suggestion when we moved from a site with a wiki to SharePoint modern: https://sharepointmaven.com/how-to-build-an-awesome-knowledge-base-wiki-in-sharepoint-online-using-modern-pages/ I used the highlighted content widget on landing pages and custom views to collect pages and provide some custom options too. But a more wiki like version of SP would be even better!
S 4 commented
My organisation has now switched to using confluence due to the lack of wiki functionality within SharePoint. The community has been extremely patient but this now needs addressing and implementation or you will loose more customers.
Can you make sharepoint wikis (or even something outside of sharepoint) match the functionality of Microsoft Docs? It has everything we're asking for!
Jimmie Traylor commented
I agree Wikis need to be updated. While I have grown accustom to how SharePoint wikis are lacking, my company is not on board with using them and is using Confluence instead. I like the idea of having one system and SharePoint should be that one system since we are now bound to it forever since going to SPO
Wiki.js and Bookstack are open source, throw them a decent donation and a contribution note and call it a day. You save yourself the embarrassment of working on this for nearly a decade and outputting something that looks like a freeCodeCamp Heroku project (Forms). I know your design team loves whitespace and pastels like we're all using 50' UHD monitors with a 30 trillion to 1 contrast ratio, use something that's already made and user friendly. You're no stranger to taking open source and integrating it (WSL).
I can't believe SharePoint can't properly handle the knowledge center (aka wiki). Along with an intranet it is a starting point for all content migrations for the companies I have worked with. Currently both of the things are hardly achivable with total O365 environment. Insane!
I read today that there will be a wiki function in the "cortex" project. that would be these "topic pages". Will the development for sharepoint online based Solution then be stopped? or are there two Solutions?
"How about the ability to add another "Site Pages" so we can separate the News and Wiki for permissions/template purposes? We can make our own modern page templates and save them for future use, but can't get them into another library. I can't even get the content type to work in a new Document Library. Even that would be a start."
And the link function []