Have a hierarchical Wiki with child wiki pages in channel wiki tab
Can you add a child wiki page in a tab so you can create a hierarchy of wiki pages so it is easily navigated and organised. i.e. more like a navigable website. At the moment you can only add a flat list of wiki pages in a channel Wiki tab. See Confluence by atlassian.
Thank you for your feedback! We support adding multiple pages to a single Wiki tab by choosing the “Create a new page” button on the bottom of the Table of Contents pane. This pane can be opened by tapping the menu button on the top-left of the Wiki.
We’re working to make the Table of Contents easily accessible on larger displays so that this option will be just a single tap away!
Yes please vote as that seems to be only way to get MS attention.
Even if you might not use a Wiki today you might need it in the future so leave your vote!
Microsoft why is this not getting any attention. Of course people will loose interest when they see a thread 3 years old without any response from you except a workaround that you guys feel is good enough.
Funny enough we use Azure DevOps as well and there you have exactly what we are looking for, how come you created in TFS/DevOps a useable Wiki but not in Teams?
Its not like you don't know how to make one, makes no sense what so ever.
More people need to vote for this
Justin Davis commented
So -- seeing as this original post is 2017, i guess this has been given up on? My company just started using Teams and i was excited when i heard there was a Wiki Function -- not so much now as this is less a wiki function and is just a Notes section. Wikis must have hierarchical organization of their children in order to be useful. I'd have hundreds of pages of documentation without a way to organize them.
David G. commented
Has Microsoft given up on creating an actual, working Wiki? From the comments from the last year or so it looks like Teams Wiki is not an option for sharing documentation across team(s).
I absolutely need some kind of information/page hierarchy or there is no point in using the "wiki" feature.
Is anthing being done about this?
I'm shocked you have the gall to call this a wiki! And your suggestion that people simply create a "Table of contents" shows you've not understood what everyone is talking about
your answer is not a solution, we understand you can create 1000 pages under a Wiki tab but for larger and more complex documentation it is just not a good solution.
To make documentation readable you cant put everything on one there has to be level of hierarchy, just look at the following example:
- Engine (Page)
- Pistons (Page)
the following page hierarchy makes sense
as it is today make no sense.
Also as somebody also said to be able to move a wiki page or pages from one wiki to another is also a very important feature.
You might have a project that is used to develop a function, once that project is done all the info needs to be moved to another team and wiki as the function is put into production.
Today it is just way to much of an hassle to work efficiently with documentation in teams, Teams have a great concept but it is just missing business oriented functions like this to be practical in real life.
Ron Allen commented
Closes I have found is to use the OneNote windows desktop application on the desktop as it supports[[links]] to create sub pages and have that shared on teams.
The one note in the cloud lacks a lot of the same functionality... especially [[links]]
jeremiah rounds commented
I want to add notes for three re-occuring meeting series in the wiki.
Meeting series A
Meeting series B
meeting series C.
I add my notes as pages to a wiki "meetings".
Make a new page for each series
Meeting series A (page), Meeting series B (page), Meeting series C (page).
Then in each page I started a section with the date.
May 1st Notes, etc
In each section I took notes...
Then one day I wanted a subsection for that days meeting. Cannot do.
Alternatives don't make any sense. If I make each series into a wiki I can page the days and then use the sections to break apart topics in the meeting, but then I have 3 wikis. If I make one wiki I mix multiple meeting series notes which is a mess in the long run.
Best solution is just to forget about sub-sections of sections and keep what I have, but it felt bad enough that I ended up here.
OneNote evidently has the same limitation insofar as how it is presented in Teams.
Roel Teeuwen commented
Absolutely useless wiki without the ability to create a hierarchy and also have the wiki menu option to default expand (so the different main wiki pages are showing)..
Anthony Rivich commented
Not sure how this is even a wiki
This is nuts! New to MS Teams. Am I missing something?
Trying to use the so-called Wiki function, but it doesn't seem to line up with normal basic Wiki capabilities. This thread is the best discussion I've found of the issue, but doesn't show much progress since it was started 3 years ago. :-(
It is now mid-2020 and we still don't have hierarchical Wiki, with sections that can expand / collapse. At least I can't find it.
@Mark - We looked today, Feb 2020.
There is a New Page button at the bottom left of the Wiki page now.
Hierarchical content is a must, as is version history (see other idea about this).
The word "minimum" from MVP, is being redefined by this product. Or maybe we should just get rid of the V out of MVP to describe Teams.
Jim Cardwell commented
I agree with most of the other comments - it really needs to be allow hierarchical content and easier to link a word to a new page - like most other wiki designs. Also, links to additional pages don't always work; this is not really usable as a wiki.
Carina M commented
I have four pages in my wiki and already this looks messy enough to completely turn me off using it. I don't want everything in my wiki as a top level page. Information naturally has hierarchies and we need to be able to work with those for a wiki to be at all useful.
Matt Heck commented
And yes, the suggestion from the then-current product manager-- perhaps he has since been replaced-- clearly indicates that he either does not understand, or is not paying attention to, this problem. He is clearly picturing his design being used by an organization that has, what, ten pages in their wiki?
He needs to be picturing HUNDREDS of pages, maybe thousands. That's how wikis work best: rapidly breaking detailed information out into its own page, with a link, so that you can quickly get to the details _if you need them_, and read right over the link the rest of the time. But that-- correctly-- results in a large number of pages, which then need to be hierarchically organized. That is normally done using an expand/collapse system that supports drag and drop, along with a few other housekeeping tools that can be a little more buried in the UI if need be, because they're not needed as often.
As far as I can tell, ALL of that is completely absent from this "design". This looks like more like a monthly coding project than a mature application.
Matt Heck commented
I am both personally and professionally offended that Microsoft is willing to call this a wiki.
The lack of hierarchical organization means that it's totally useless for anyone trying to rapidly assess what information is in the system, a critical capability for new personnel on a project. The lack of rapid insertion of inline links to existing pages is utterly inexcusable-- that's what a wiki _is_. Finally, the fact the wiki isn't even mentioned in the training material tells me _exactly_ how low a priority it is for Microsoft.
My guess is that this thing is deliberately crippled to avoid competing with Sharepoint. But the resulting product literally disqualifies itself from its own name.
The result is not competitive with a real wiki.
Nick W commented
The Try this instead isnt helpful. Subsections needed - without it, its useless.