Invision end-to-end flow when installing Penny University in a new slack

[JnBrymn]

Goal

We are missing several key ingredients in deploying our platform to other communities. This ticket is a brainstorm of the lifecycle of the application. The results of this ticket are a discussion and then additional tickets that belong in this milestone. Below, bold is probable tasks that we need to work on. Italics is questions that we need to resolve.

We also need to submit our app to the market space.

Steps

• Needing and then Searching for - companies/communities that are looking for a way to get members to know one another better would search for us.
  • They would eventually land on our homepage which is currently missing a crisp description of our offerings (because we don't know what we will offer yet). Compare donut.com
  • Once we get a little brand recognition then they could go directly to our app page (which doesn't exist). Compare donut.
  • Question: what keywords would they search for?
• Installing
  • Slack admins will be shown a permissions screen. We probably need to do exactly what Donut is doing.
    
• Deploying We get a chance to onboard the admins. This should be an opportunity to set up the initial chat rooms and otherwise configure interactions. As seen in Donut
  

then

• Admins get their own get their own application to control the slack integration
  
• Onboarding users automatically
  • We can do this through the rooms we create: #how-do-i, #book-club, #virtual-coffee (but with more need-aware introductions than donut)
• Integrating with broader community - e.g. introduce each slack with the experts from other slacks. We don't have to do this immediately, but it has to always be a possibility.