Public Slack Community Invite

Building Public Slack Communities – Slackvite Launch

I had the urge to build and ship something since I gave Hey Kramer to the world.

Bot Slack RTM API

Something … useful.

Since I was already elbows deep in the Slack API, I decided to build a thing that lets you “launch and manage public Slack communities in 30 seconds”. I say “manage” liberally because at this point it does none of that (the ideas list is already getting long).

But, you can launch a fancy pants landing page that pulls beautiful background photos from Unsplash to gather invites for your public Slack community. So, that’s a start I suppose.

Public Slack Community Invite

Is this a new idea? No.

There are a couple excellent solutions for building a public Slack community platform. For instance if you are reading this you’ve probably already stumbled on Slackin. It’s a great solution, however I built Slackvite for those of you that get scared away by landing on a Github page. If seeing ‘.travis.yml’ and ‘app.json’ files frightens you then you might like this.

There’s also the also very capable and popular Typeform hack for creating a Slack community. But again – if code scares you it’s not for you.

With Slackvite you just 1) register 2) connect with Slack 3) select your team 4) launch your public invite landing page to the world. Here’s a demo for an Iowa State Cyclones Slack community.

Slackvite Public Slack Community Invite Landing Page

Published by

Andy Brudtkuhl

Andy is a web developer, entrepreneur, bike commuter, seinfeld quoter, and daddy to two little girls and three dogs in Des Moines, Iowa.

2 thoughts on “Building Public Slack Communities – Slackvite Launch”

  1. I like this part: “In case you’re scared of code.” I’m not afraid to go behind the scenes a bit into the source code, but ultimately I leave that to the professionals. I know enough to be dangerous and that’s good enough for me.

    What’s interesting about what you’ve done is that you’ve templatized a platform; you’ve made it simple for anyone to implement without much added stress.

    And THAT’S what people want. If they’re savvy enough to pull from a Github repo and implement on their own, they’ll probably just do that.

    1. Hey Mike – that was the entire goal! I’d guess with Slack’s increasingly broad user base there are going to be a lot of non-technical people wanting to create public Slack communities that don’t know how to setup Heroku, clone a Github repo, and configure API keys 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *