[Twisell]

My boss is deseperately trying to convince me that my project wiki can painlessly be replaced by Microsoft Team (build upon share point). Yet this is utter bullshit every workaround he proposed to replace missing feature look like regressions that will make us spend more time on solving share point issue than on actually writing documentation.

You seems satisfied with FB for business and you claimed it could advantageous replace multiple wikis. Can you develop your though cause from the outside it look like the same bullshit that salespersons will use to sell MS Team to gullible boss.

[krylon]

> My boss is deseperately trying to convince me that my project wiki can painlessly be replaced by Microsoft Team (build upon share point).

In my experience, the words "SharePoint" and "painless" do not exactly go well together.

[underwater]

Facebook Work is a communication tool. It doesn’t replace your wiki. The only real affordable is Notes, which solves the “update email” case, but not evergreen documentation case.

Facebook use Quip for wiki-like solution as well as some internal tools.

[Twisell]

My bad op mentioned that they kept wiki for doc. Read to fast sorry.