Integrate the bot and web app more

[ghost]

todo

• /penny chats - goes to the all chats page https://www.pennyuniversity.org/chats/
• /penny chats @JB - goes to https://www.pennyuniversity.org/profile/3
• /penny chats me - goes to https://www.pennyuniversity.org/profile/

[mrshwah]

For /penny help, I would just return the list of commands in Slack, which then could lead them to use the others to get into the web app. It would be a strange UX to be taken out of slack for that when I'm wanting to find out what the slack app itself can do.

[JnBrymn]

I agree w/ @nchouard regarding /penny help. The functionality of the others I think is great. I've actually needed it quite a bit. But I would recommend consolidating. Rather than /penny chats and /penny profile what if we just had /penny chats which could optionally be followed by a user name.

• /penny chats - goes to the all chats page
• /penny chats @nchouard - goes to Nick's chats
• /penny chats @me (I just checked... this works in slack) - goes to my chats

I like consolidating in that it's one less command. However it does inconsistently go to the profile page some times and to the chats page some times. That's a little annoying.

[mrshwah]

I like that idea @JnBrymn.

[JnBrymn]

getting started

• Set up your dev environment.
• When you type /penny chat in slack, slack sends the information here.
  • You'll probably want to create a chats elif clause and a new BotModule kinda like PennyChatBotModule (which is defined here)
• Within the processor all you have to do is 1) if a user was not provided, then return a link to the chats page https://www.pennyuniversity.org/chats/ 2) if a user IS provided, then you'll need to get their social profile id (from here) and return their profile URL https://www.pennyuniversity.org/profile/3.
• You gotta make it look pretty using slack blocks rather than just a plain URL
  • block docks
  • blocks WYSIWYG builder
  • here's us building blocks for chat invitations like you see here.