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!
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.
We've just started using teams and loving it - The Wiki seemed like the perfect solution for what we needed, and I even started building the Wiki. But quickly realised that without Sub-Sections and Sub-Sub Sections, the effectiveness of the Wiki becomes limited very quickly. Is this likely?
This just adds a page to the main tab. There is no hierarchy which makes this wiki quite useless
Supporting adding multiple pages is not what is being requested here. We want to organise those multiple pages into a hierarchy, much like the Confluence wiki.
I would like to drag and drop my multiple pages around this hierarchy using the table of contents. I'd like to right-click a section to create a sub-section.
I'm trying to set up a company-wide wiki much like I can do in Confluence.
This means I need the following hierarchy:
> Multiple Projects
> .....Multiple sections (like project overview information/related customer information etc.)
> ..........Multiple sections (breaking down that project information)
> ...............Multiple sections (further breaking down that project information)
> .....................etc. Without a limit determined by MS.
Garrett Fuller commented
You can only make the nesting 2 levels deep. That is shockingly useless. Without more ability to fluidly organize information, it is just a list. I might as well keep the information in a sticky note.
Microsoft... yet another almost good product. I would love to be able to do away with having a Slack. Just sign into my Microsoft work account in the morning, and be good to go. I imagine that is what you are trying to enable. But the tools have to be useful enough to invest energy into them.
Even the most basic project will have information too complex to represented with 2 levels of nesting. Worse than useless.
Sigh, looks like Microsoft is ignoring everybody. This isn't a wiki, totally unusable. I can get free software that is 100 times better
Aman Arora commented
There is only a 2 level hierarchy - pages and then sections underneath the pages. Why not allow creating sub-sections? I think we should have Pages -> SubPages -> Sections -> SubSections.
It's not a wiki if you can't create a hierarchy. Right now it's just a document.
Teams Wikis need this functionality, wikis arent very useful without it, think a IT knowledge base for example, you wouldn't have all the articles in a continuous list, you'd have categories like Vendor > Products > Articles otherwise you just a have a list of articles for every vendor all mixed up..
As a user of the wiki I would like to be able to create a hierarchy of wiki pages that can be organised into groups, so that I can more easily navigate the sections and subsections of my wiki.
As a user of the wiki I would like to be able to create a special TOC page from a template when I create a new page, so that I can more easily navigate a large wiki.
Maybe adding anchors within the sections will solve for an additional layer of hierarchy? Maybe structured like Wiki>Pages>Sections>Anchors.
Frédéric Beuserie commented
mark, you definetely not respond to the question.
what we need is a hierarchy, not a flat workspace !