Add info to slack migration docs #6788
Conversation
|
Newest code from mickmister has been published to preview environment for Git SHA 440ae66 |
|
Thank you, @mickmister! Let me know how best I can support you with this lift, and please feel free to reorder the content on the page based on your initial feedback. |
|
Newest code from cwarnermm has been published to preview environment for Git SHA 9aa2cb8 |
|
@cwarnermm I think doing a side-by-side comparison of the two versions of the rendered docs would be helpful. The markdown diff makes it hard to inspect the new changes, and seeing the new version without the context of the old will be difficult to know what the changes are |
|
Newest code from cwarnermm has been published to preview environment for Git SHA cd69b48 |
|
@mickmister - I've reorganized the content on the page based on your excellent feedback in my commit. Also adjusted minor formatting to align with the documentation style guide. |
|
Newest code from cwarnermm has been published to preview environment for Git SHA 0a9747a |
|
Newest code from cwarnermm has been published to preview environment for Git SHA b2186c4 |
mickmister
requested review from
cwarnermm
and removed request for
cwarnermm
|
Newest code from mickmister has been published to preview environment for Git SHA 954eb44 |
|
@cwarnermm FYI I created an issue to remove the marketing verbiage around bespoke #6816 |
|
Newest code from mickmister has been published to preview environment for Git SHA 8f52948 |
|
Newest code from mickmister has been published to preview environment for Git SHA 1fb5e13 |
|
Newest code from mickmister has been published to preview environment for Git SHA e66ffc0 |
|
Newest code from mickmister has been published to preview environment for Git SHA 4ab658c |
There was a problem hiding this comment.
@mickmister fantastic job man! I found this one to be a gnarly one to lay out... you have a nice flow through that incorporates all the related tools (except maybe one... see below).
One case I'm wondering about is when a customer is merging multiple workspaces, and what should our guidance be here... do we add considerations for this right on the same page, or link of somewhere else as an "Advanced Topic". This is a gnarly topic itself, and introduces the need for the sync tool you built to help address user merge issues.
| 8. Grant the app permissions when prompted. | ||
| 9. Copy the **Bot User OAuth Token** and save it somewhere convenient. | ||
|
|
||
| We'll now use **Bot User OAuth Token** with the ``slack-advanced-exporter`` tool to download emails and attachments. Download the latest release of ``slack-advanced-exporter`` for your OS and architecture `here <https://github.com/grundleborg/slack-advanced-exporter/releases/>`__ and extract the executable from the download. |
There was a problem hiding this comment.
I think we should move it to the MM org and commit to owning issues with it.
mickmister
dismissed
fmartingr’s stale review
I'm addressing the remaining screenshot request from Felipe. Wanting to get this merged today so dismissing his review
…ttermost/docs into slack-migration-docs-michaelk
|
Newest code from mickmister has been published to preview environment for Git SHA fbc46d6 |
|
Newest code from mickmister has been published to preview environment for Git SHA 352b601 |
|
Newest code from mickmister has been published to preview environment for Git SHA acfe878 |
This reverts commit acfe878.
|
I reverted adding the screenshots, as that is specific to only exporting public channels from Slack. I think customers will mostly be doing the full export, which those screenshots don't help with, so I think they will more of a distraction than anything, especially because of how big the images are rendered on the docs page |
|
Newest code from mickmister has been published to preview environment for Git SHA 9224dea |
|
Follow up ticket to move https://github.com/grundleborg/slack-advanced-exporter to Mattermost org |
|
Newest code from mickmister has been published to preview environment for Git SHA a520ffa |
Summary
This PR fills in information in the Slack migration docs to reflect findings in my experience with migrating from Slack to Mattermost
Ticket Link