![]() ![]() The method for creating these, though, will be via markdown. We expect to remedy this over the next few months so that anyone using the new view will be able to create tables and emoji. This effects anyone who doesn't yet have the new issue view for full-page issues. Due to technical constraints, some of you currently won't be able to create tables and emoji in the new issue view. The first is regarding tables and emoji in the new issue view. His thoughts on the matter may help you decide whether wikis or notebooks are the best fit for your Team(s).There are at least two related but distinct themes on this issue, so it's important that we address both of them to avoid any misunderstanding. Still aren’t convinced?īob Morris has done a very impressive and thorough job of comparing the two. You’ll want to repeat these steps for each new channel you create and, as mentioned, consider creating a new notebook section for each channel to keep things simple, organized, and easy to navigate. That’s it! Just a few steps and you’ve substantially increased the productivity potential and collaboration superpowers of your Team. Use the tab dropdown menu to rename the probably-very-long name to something simple like ‘Notebook’ for a cleaner user experience.(I recommend mirroring your notebook’s sections to your Team’s channel structure) ![]() ![]() Select the Notebook, and if for a channel other than general, perhaps a corresponding section in the Notebook.Click the plus sign (+) to add a new tab and select OneNote for the tab.Use the dropdown menu for the Wiki tab and select Remove.So then you’ll have a simple ‘About’ tab for Team information and a ‘Notebook’ tab for ongoing collaboration and work. Matt Wade suggests renaming the wiki tab to ‘About’ and using it as a reference/resource for the Team itself in his Definitive Guide to Everyday Etiquette in Microsoft Teams. While I’m suggesting that OneNote be used for your Team’s note-taking, collaboration, and regular information sharing in a highly mobile and flexible medium, there is still a case to keep wiki alongside OneNote. There are more reasons, like how robust you can get with formatting text, but I think you get the picture.OneNote supports drawing/writing with styluses (styli?).Try searching your wiki or restricting certain parts without creating a private channel. OneNote is easily searchable and can have password protected areas.This can get messy reassembling and manipulating. Wikis are folder structure document libraries in your site’s Site Contents folders.Notebooks can be moved, migrated, archived and accessed later more easily as a standalone OneNote file.Notebooks and Wikis are both stored in SharePoint (not Teams).I typically recommend new Team owners (or admins setting up new Teams) delete the ‘Wiki’ tab that comes with the Team and insert a new OneNote tab called ‘Notebook.’ Why replace the wiki with OneNote? The wiki tab that is added to every Team and each of its channels is convenient, but not robust and its content is not easily migrated and shared. ![]()
0 Comments
Leave a Reply. |