Links to docs unfurl poorly in Slack

[cwjohnston]

When someone posts a link to our documentation into Slack, the page is crawled for metadata which is used to "unfurl" or provide a synopsis of the linked content. Right now it looks like this:

The unfurled message is the same for every page on our site, which makes these synopses obnoxiously repetitive. We should follow the instructions provided by Slack to make them useful.

[apaskulin]

b477814 produces https://gist.github.com/apaskulin/428ceec6805dbea20b2610401c760430

Working under a theory that a smaller image will render in-line with the text instead of expanding below (see unfurl for slack.com), but still looking for a way to test this.

[cwjohnston]

@apaskulin On the face of it your commit looks 💯 to me! If it proves too difficult to test, perhaps we just roll with it and revert if needed?

[obfuscurity]

I agree with Cameron, let's and see how it goes. I can also run it by Emerson Stone if you'd like a 3rd opinion from our design consultants.

[apaskulin]

PR is ready (#515) for a first try at this. As a sidenote, Hugo offers a wealth of page-specific variables for this type of use case, including page summary (the first 70 words on the page), reading time, and word count. I left these out of #515 in an effort to keep unfurls brief and reduce noise, but I'm open to feedback if there's something more you'd like to see in an unfurl.

[cwjohnston]

The end result of Alex’s first pass in #515 looks great when unfurled in slack, so I think we’re done here. If we need to iterate on this further, let’s open a new issue.

[obfuscurity]

<3

…

Sent from my iPad

On Jun 22, 2018, at 3:54 PM, Cameron Johnston ***@***.***> wrote: The end result of Alex’s first pass in #515 looks great when unfurled in slack, so I think we’re done here. If we need to iterate on this further, let’s open a new issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.