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.

477 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 →

    48 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

        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.

      • Ivan commented  ·   ·  Flag as inappropriate

        We need support for Markdown to be able to migrate from an old Wiki product that we're currently running internally.

      • Ernest Correale commented  ·   ·  Flag as inappropriate

        The SharePoint Wiki is HORRIBLE!

        1. There are no text macro options for types of content within the wiki page
        {code} this is my code {/code} should display the content in the {code} block with custom formatting as defined out of the box or as defined by the user. Macros could include options for Code, Lists, Display Panels, Contributors, etc. For a list of examples, see https://confluence.atlassian.com/doc/macros-139387.html

        2. Ability to create custom templates for Wiki pages. That doesn't mean fire up visual studio, write some convoluted powershell to be run on the server or, hire a team of developers because it’s a “framework”! We are all sick of that nonsense. We want a way for end users to actually create a wiki template for their business use similar to the way they would create a MS Word template. It should not take a senior-level support engineer 3 days to create a custom template in code.

        3. Why can’t we copy and paste an image into the Wiki page? I mean, really?? Lack of this feature is one of the issues killing user adoption for my org. Most of them hate the Wiki and I cannot blame them.

        4. NAVIGATION! For the love of GOD why is navigation so freak'n difficult in SharePoint!! A user has a Wiki site with nearly 600 pages in it. She wants to create a navigation structure so users can find stuff by category. She has 30 pages tagged with the metadata term "Foo". I would think that she could easily create a table of contents page for all pages categorized with the metadata. Except adding a TOC web part results in nothing but broken links. Obviously, someone forgot to tell the developers that a list of broken links really isn’t really a viable solution.

      • Adriaan Van Nuffel commented  ·   ·  Flag as inappropriate

        When you want to link in a Wiki to a document from a library - it should be like this:

        - open page editor
        - click an "Add link" button
        - in the popup window -> possibility to browse through the files of the libraries and choose the file you need

        It's like that in Word, and seems logical and easy to me.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I think MS may miss the point again here. The wiki in SharePoint is unusable by normal people and millennials. As a result, people prefer tools like Confluence. The issue is not just layout, it's also navigation. Look at Confluence and see why that is preferred by many.

      • Kyle commented  ·   ·  Flag as inappropriate

        Hi SharePoint Experiences Team,
        I read the complaints in here and most of us are asking for improved features in the SharePoint wiki. Can you please explain what/how "Adding wiki functionality to Modern Pages is in our plans" relates to the "A Total Revamp for Wikis" idea?
        Thanks.

      • Dan M commented  ·   ·  Flag as inappropriate

        OneNote integration and also consider making it like docs.microsoft.com

      • QF commented  ·   ·  Flag as inappropriate

        Without a proper wiki, Sharepoint is not a real collaboration tool.

        I don't know in which product Microsoft wants to put a proper wiki. Here I mean a confluence style wiki which really encourage collaboration. A mediawiki (wikipedia) is not sufficient.

        Onenote has inherent problem as it is a file. It is slow to open, and when it gets bigger, it becomes slower and slower.

        There is a wiki in Teams, it doesn't offer anything more than what a OneNote could offer.

        I have used confluence wiki for ten years, the original version is basic but adequate. Here are some important features that encourage people to use it (many are super simple) - show most popular pages, show modified date and user, easy to compare and restore versions, different way of sorting pages (creation, modified, file name, etc.), full search possibility, possible to show (embed) a page in another page (single source of truth).

        Would love to help with Sharepoint wiki development

      ← Previous 1 3

      Feedback and Knowledge Base