SharePoint
Feedback by UserVoice

I suggest you ....

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.

619 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Antonio Segovia shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    59 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        page categorisation is very lacking in the SharePoint wiki, can something be done about this also?

      • Kazzan commented  ·   ·  Flag as inappropriate

        I hope, that wiki will be also nice like others new document libraries.

      • Garrett H commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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.

      • Alex commented  ·   ·  Flag as inappropriate

        +1

        Yes, Microsoft Document pages were the ideal wiki for SharePoint :-)

      • Anonymous commented  ·   ·  Flag as inappropriate

        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
        versioning
        Rapid TOC and page creation.
        linking

        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.

      • Roy F commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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?

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Mo commented  ·   ·  Flag as inappropriate

        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.

      • Fanny commented  ·   ·  Flag as inappropriate

        Hope Microsoft really can do somethings to enhance on the Wiki site user experience.

      • Ben Christian commented  ·   ·  Flag as inappropriate

        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.

      ← Previous 1 3

      Feedback and Knowledge Base