Stop storing wikis as mht files
Storing wikis as compiled html files is ... lame. We can't edit them on the sharepoint site. Store them as markdown files so we can alter them outside of the (terrible horrible awful lousy stupid inane lame poor disgusting putrid detestable vile) wiki editor
Karsten Schäffer commented
Please adopt Wiki from Azure DevOps.
That one is much better with its .md files directly accessible through a git repo.
Jorge Fernandes commented
In fact it is crazy - no export to any other format. I'm trying to send my report made in a wiki and I can't neither give them permissions to my colleagues access the UI of the wiki nor made a file to export. When I choose "open in an application", word open it but loose all the images references. How can I take my content from a wiki in teams without the need to reformat all the content or introduce again the images?
Michael J. Ryan commented
Agreed, this would be SO much easier to use any number of tools if these were .md (markdown) files... I know conversion would be an issue, and could even be limited to touched wiki entries and convert on update, or trigger... but would really love if they were just .MD files, especially given that the interactions on Teams itself is really markdown centered.
GFM as a preference with tables.
Search function in Teams is terrible due to these mht files.
When a user is able to find a page using the search function in Teams, the search result is presented under `Files` as mht files. And than there is the message `Hmm… looks like this file doesn't have a preview we can show you`. Downloading this file is the only (stupid) option.
Every user expects to get a search result he/she can open for reading with a mouse click.
Agreed! Well done on re-inventing the wheel badly!