Skip to content

Commit 0a76fd0

Browse files
committed
updated WFH post images
1 parent 71ef6bb commit 0a76fd0

File tree

3 files changed

+15
-14
lines changed

3 files changed

+15
-14
lines changed

_posts/2015-11-03-november-wfh-slack.md

Lines changed: 15 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -4,33 +4,34 @@ title: Working From Home Slack Bot
44
author: Mike James
55
categories: [hacks,javascript,node, slack]
66
---
7-
So back in June we had a hackday and produced an initial release of what we call WFH (working from home) bot (see [original post](/blog/hack-day-wfh-bot)). We have a remote working policy, so rather than having a long WFH email chain being sent individually everyday we've built a system to help. Slack is core to all internal chat communications and everyone uses it. It also provides a flexible API which makes it good place to interact with WFH.
7+
Here at pebble{code} we have the freedom to work remotely. It's been a part of our culture from the early days. So back in June this year we had one of our hackdays and produced a service we call WFH (working from home) bot (see [original post](/blog/hack-day-wfh-bot)). The idea behind the hack day was to try out some new tech and solve some problems along the way. The bot helps prevent long email chains on who is working where. Slack is core to all internal chat communications.
88

9-
The first version of WFH was private on Github, today we're releasing it as OpenSource. As we figured this might be useful to other people working remotely. This post documents the recent changes and features. Its here for you to play with and [host your own](https://github.com/pebblecode/wfh-api).
9+
The first version of WFH was private, and today we're releasing it as OpenSource. As we figured this useful! So its here for you to play with and [host your own](https://github.com/pebblecode/wfh-api) under [MIT](http://opensource.org/licenses/mit-license.php).
10+
11+
###Architecture
12+
![image of architecture](/img/posts/2015-11-03-wfh-slack/diagram.png)
1013

1114
###What's changed?
12-
We've had a play around with the api and had some interations, we've also experimented with one version in Erlang. We've settled at the moment for a node.js version, as most of us devs here at pebble write JavaScript. But we're going to continue playing with Erlang as its an interesting platform.
15+
We've had a play around with the api and had some interations, we've also experimented with one version in Erlang [here](https://github.com/pebblecode/wfh2_backend). We've settled at the moment for a Node.js version, as most of us devs here at pebble write JavaScript. But we're going to continue playing with Erlang as its an interesting platform.
1316

1417
#### Parameters
1518
We now have parameters in the slash commands.
1619

17-
`default: (wfh,wfo)`
18-
Allows you to change your default status. Say for example you change; to working from home by default and come to the office less frequently.
20+
`default:wfh` or `default:wfo`
21+
Allows you to change your default status. Say for example you change, to working from home by default and come to the office less frequently.
1922

20-
`message: I'm at a conference`
21-
messages allow you to give some description.
23+
`message: I'm at a conference` or `message: I wan't to sit in my pants all day and work from home`
24+
messages allow you to give some description.
25+
26+
![Screen shot](/img/posts/2015-11-03-wfh-slack/screenshot.png)
2227

2328
####Statuses
2429
We have InOffice, OutOfOffice, Sick and Holiday. All statuses last for a full working day. Say you want to set the status for your next day at work to another status you can do that after 8pm as we figured most people won't be updating their status for the current working day at 8pm.
2530

26-
27-
###Architecture
28-
![image of architecture](/img/posts/2015-11-03-wfh-slack/diagram.png)
29-
3031
###Integrations
3132
The api has full CRUD functionality, see the docs for more details. So this is open for your own integrations. We've used this to integrate with [Tribe HR](https://github.com/pebblecode/tribehr-holiday-fetcher) and [send Emails at 10am](https://github.com/pebblecode/wfh-email-cron)
3233

33-
###We'd love to hear from you
34-
Let us know what you do with WFH bot.
35-
34+
![TV](/img/posts/2015-11-03-wfh-slack/tv.jpg)
3635

36+
###We'd love to hear from you
37+
We're pretty proud of our WFH bot, we can see various features being added over time. Its pretty simple to extend its a [hapi api](http://hapijs.com/). Do let us know what features you'll like to see with WFH bot.
32.4 KB
Loading
815 KB
Loading

0 commit comments

Comments
 (0)