This data as json
| day | description | everyone | facilitators | facilitators_twitter | id | length | notepad | room | time | timeblock | title | transcription |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Friday | Do I use "display" or "position" for that? Sometimes you just want to make sure your newsroom tool does it's job and not have to worry about what it looks like. Well, your days of worrying about front-end design could soon be over. Slack's suite of API's are vast and the documentation is one of the best of any API out there. In this session, I'll quickly demo most of the different methods of interaction available with Slack's APIs. We'll build a simple graphics request form together as a group. When that's finished, we'll brainstorm ideas for other newsroom tools and discuss how our front-end needs could be met by one or more of the methods we've seen so far. We'll be using Flask to do it, so basic Flask and Python knowledge will be required. Slack has a number of features you might need from a front-end design already included. Unprompted function calls? Slack has slash commands. Do they support arguments? You bet they do. Filling out forms? Slack's got that too. Giving personal user feedback when a script runs? Ephemeral messages make sure that only a single user can see the notification without ever having to leave the channel. Learn about all these and more in the session. We'll use [this sandbox Slack workspace](https://join.slack.com/t/srccon2018frontend/shared_invite/enQtMzg3ODM3NjIyMTAxLWVkZWI4NGFkYzRlNmZiMGU0N2U4NjBmMmY0Zjg1NjRmNGFiNDdkY2E2NDczMjA3ODA4YTk4ZTNiYzI1MDk4YmU) during the session, so feel free to go ahead and join! | Andrew Briz | brizandrew | slack-as-frontend | 75 minutes | y | Minnesota | 2:30-3:45pm | friday-pm-1 | Who Needs A Front End? – How To Leave The UX of Newsroom Tools to Slack |