Drop the "Wiki"
Multi-Wiki considered harmful. Our company already has "a wiki". Then Microsoft Sharepoint encourages a proliferation of "wiki" sites, and now we have another entirely separate place for more "wiki" pages.
The main advantages of a wiki are:
1) everyone can participate -- any problem or oversight can be corrected by any user
2) search -- finding things is easy
Having an endless supplies of wikis, where you can't search between them, and not everyone can even view them all, seems to defeat the main benefits of a wiki. Now every channel, in every team, has their own "wiki". And they're "private" by default.
Not only that, but it's namespace pollution -- if you tell someone to update the wiki, how do they know which one?
PLEASE, drop the "feature" of having a wiki from this software.
If you had implemented a full contact system, with support for multiple addresses, and pseudonyms, for every user of the system, that would be terrible. Because Microsoft Teams is not the place for it. Hopefully the product manager would see that, and fight to remove it. I see having a "wiki" in MS Teams the same way.
Joel Elliott
shared this idea
30 comments
-
Nicholas
commented
I disagree - I want control over multiple sub-wikis for each team. (but with improved, real wiki features)
However these should optionally be aggregated up into some "Unified Corporate Wiki" so that information is discoverable to the organisation. -
John Baldwin
commented
Don't drop the wiki... BUT...
1. Rename it to "Pages." It's just a set of editable pages with a few minor formatting options thrown in. (We happen to use this heavily but it is NOT a wiki.)
2. Give the owners of each Team or Channel the option of easily removing this tab. As seen below, there are organizations that already have real wikis (or at least are using SharePoint... also NOT a wiki !!) and they don't want colleagues putting stuff here instead.
3. How about giving us easy integration with a REAL WIKI? One that is searchable, easily editable, supports full markup, and MOST IMPORTANTLY.... the ability to write dangling links!
REAL Wikis are super easy to edit and super easy to move content around. And most importantly you can write a dangling link in the page you're editing, then you can go back later, click on that link, and create the page it points to.
-
Anonymous
commented
I fully agree that the "Wiki" name should be dropped. The "Wiki" is a misnomer at best. However one might also call it a trip back to the dark ages of "embrace& extent".
It is sad because I am having a hard time explaining to some Microsoft-only users that the problem is not that wikis are ****, but that MS's implementation is not a wiki. Also they don't "get" the importance of the missing features.
-
Anonymous
commented
Reconcile all usefull thoughts from this thread an reconsidder WIKI within teams. Especially because it uses MHT as pages en does not in any way integrate with the sharepoint WIKI and well known browsers.
Within Teams OneNote should be enough. WIKI should be done the sharepoint way.
-
Marc NainNo commented
The least usefull app on microsoft teams.
Developped by a ten years old child i think.It is only a plain text box without search or interest.
Just put a one note.
-
Dan Hamilton
commented
This isn't a wiki, it's a simple page creator with basic rich text capabilities. It's embarrassing to call it a wiki. You should just rename it to something else to reflect it's extremely basic feature set and integrate the classic SharePoint Wiki template as a subsite of the site collection for the Team.
Here are some features that normal wikis have that this "page with rich text" non-wiki does not.
1. Search
2. Review
3. Moderation
4. Permissions/Roles
5. Notification system
6. Hierarchy links/bread crumbs
7. Inherited page properties
8. Page Templates
9. Proper HTML/CSS/js support
10. Interwiki Linking
11. Referential linking
12. User linking/User mentioning
13. Rich Media support
14. Namespace definitions
15. Page meta data
16. Email integration -
Erik
commented
No, an integrated Wiki is essential, particularly when we can integrate with other tools, like Azure DevOps and Planner.
I can appreciate the concern about too many places to store information, but they have different purposes.
-
Christian Haase
commented
don't DROP wiki, but leave it to the sysadmin to whether enable wiki or disable it.
-
Anonymous
commented
I like the wiki for keeping team meeting actions in project teams sites, rather than the bloat one-note feature, that takes forever to load and is overly complex. I would not vote for killing the wiki (maybe rename as "meeting minutes" as an optional tab with very similar features to the wiki - except new entries should appear at the top of the list, rather than the bottom by default - see https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31957204-microsoft-teams-wiki-listing-order
-
Jeremy
commented
beside this, if you delete it accidentally, you can't recover it!
-
Paul Van Beek
commented
The Wiki is not useful in this configuration. At least give the option to remove it or decide whether to include it when making the team.
-
DW
commented
One NOte rules...just make 2019 One Note as good as 2016 and we'll have a solution.
-
Phylicia
commented
I'd just like to be able to disable the wiki from showing up in Teams at all. If other people like it, great. It will not work in my environment so I'd love to be able to just turn it off.
-
Anonymous
commented
I love the Wiki capability and use it extensively. I hate SharePoint with an equal passion. If you don't like it you just need the ability to turn it off not try and mess up Teams for the rest of us.
-
Anonymous
commented
I have no problem with Apps like Wiki when you can decide if it's in the app catalogue or not. When companies are using confluence etc. the default presence of a wiki tab is painful. Please make it optional to avoid chaos.
-
Anonymous
commented
I find it useful. If IT manager could hide it, then fine.
-
Mary
commented
We would like the option to disable the Wiki tab in our Teams tenant for compliance purposes.
-
Joel
commented
I use the Wiki for every channel project. Loading Onenote in Teams is too slow and too disconnected - can't call out specific notes in chat (easily). Does the Wiki need to be renamed? Yes. Which you can do for every channel, call it what you want. So, that is very useful. On some channels I rename it "Project Notes". Handy. Should Wiki somehow be integrated with OneNote and renamed? Probably.
-
Anonymous
commented
Like Ian Holmes said, just give us an option to disable this Wiki and everybody is happy
-
Sam Hall
commented
I agree, this "Wiki" feature is useless bloat. I found the feature amusing at best, especially the way you can actually have multiple Wiki's in a single channel (just to confuse it's purpose even further). Fragmented knowledge, hidden and scattered across channels really flies in the face of what a "Wiki" is about.
When I look around our Teams channels, the wiki feature's usage is limited to what I'd call sticky posts on other platforms.