Skip to content

Commit cf3875e

Browse files
RelequestualRelequestual
committed
Add readme.md for slack folder.
Add greeting slack workflow export for safe keeping (can be imported if required)
1 parent a899428 commit cf3875e

File tree

2 files changed

+115
-0
lines changed

2 files changed

+115
-0
lines changed

‎slack/greeting.slackworkflow

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
{
2+
"source_id": "414510517562912920",
3+
"version": "1",
4+
"workflow": {
5+
"name": "Greeting",
6+
"blueprint": {
7+
"version": "1",
8+
"trigger": {
9+
"type": "member_joined_channel",
10+
"id": "eec4a322-082c-4247-8cdd-b67d5eeee6aa",
11+
"config": {
12+
"channel": {
13+
"value": "C5CF75URH"
14+
}
15+
}
16+
},
17+
"steps": [
18+
{
19+
"type": "message",
20+
"id": "c795fd83-f6c7-48de-b11a-937a1702d785",
21+
"config": {
22+
"user": {
23+
"ref": "eec4a322-082c-4247-8cdd-b67d5eeee6aa==user"
24+
},
25+
"has_button": false,
26+
"message_text": "Hey {{eec4a322-082c-4247-8cdd-b67d5eeee6aa==user}}, Welcome to the JSON Schema Slack Server!\n\nWhatever the reason you chose to join us, we want you to know, we're glad you're here.\n\nWe have a formal Code of Conduct which we invite you to review. It is short, and reading it is respectful to the community you've chosen to enter.\n\nIf you need help, or you're looking to get involved with the JSON Schema community, you're in the right place.\n\nThis server includes the specification authors, many implementers, and a large number of helpful individuals from the community.\n\nIf you're looking for an implementation of JSON Schema, you should check out the implementations page.\n\nIf you're looking to learn the basics of JSON Schema, do check out our learning resources.\n\nIf you want to ask questions or discuss JSON Schema, the <#C5CF75URH|general> channel is the right place.\n\nFor details on other channels, click on the plus icon on the left of the message text area, followed by \"channel info\", or you can view the same information on our GitHub Repository.\n\nFor now, please let us know who you are, what you do, and why you've joined us today!",
27+
"message_blocks": [
28+
{
29+
"type": "rich_text",
30+
"elements": [
31+
{
32+
"type": "rich_text_section",
33+
"elements": [
34+
{
35+
"text": "Hey ",
36+
"type": "text"
37+
},
38+
{
39+
"id": "eec4a322-082c-4247-8cdd-b67d5eeee6aa==user",
40+
"type": "workflowtoken",
41+
"property": "",
42+
"data_type": "user"
43+
},
44+
{
45+
"text": ", Welcome to the JSON Schema Slack Server!\n\nWhatever the reason you chose to join us, we want you to know, we're glad you're here.\n\nWe have a formal ",
46+
"type": "text"
47+
},
48+
{
49+
"url": "https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md",
50+
"text": "Code of Conduct",
51+
"type": "link"
52+
},
53+
{
54+
"text": " which we invite you to review. It is short, and reading it is respectful to the community you've chosen to enter.\n\nIf you need help, or you're looking to get involved with the JSON Schema community, you're in the right place.\n\nThis server includes the specification authors, many implementers, and a large number of helpful individuals from the community.\n\nIf you're looking for an implementation of JSON Schema, you should check out the ",
55+
"type": "text"
56+
},
57+
{
58+
"url": "https://json-schema.org/implementations.html",
59+
"text": "implementations page",
60+
"type": "link"
61+
},
62+
{
63+
"text": ".\n\nIf you're looking to learn the basics of JSON Schema, do check out our ",
64+
"type": "text"
65+
},
66+
{
67+
"url": "https://json-schema.org/learn",
68+
"text": "learning resources",
69+
"type": "link"
70+
},
71+
{
72+
"text": ".\n\nIf you want to ask questions or discuss JSON Schema, the ",
73+
"type": "text"
74+
},
75+
{
76+
"type": "channel",
77+
"channel_id": "C5CF75URH"
78+
},
79+
{
80+
"text": " channel is the right place.\n\nFor details on other channels, click on the plus icon on the left of the message text area, followed by \"channel info\", or you can view the same information on our ",
81+
"type": "text"
82+
},
83+
{
84+
"url": "https://github.com/json-schema-org/community/tree/main/slack/other%20channels",
85+
"text": "GitHub Repository",
86+
"type": "link"
87+
},
88+
{
89+
"text": ".\n\nFor now, please let us know who you are, what you do, and why you've joined us today!",
90+
"type": "text"
91+
}
92+
]
93+
}
94+
]
95+
}
96+
]
97+
}
98+
}
99+
]
100+
}
101+
}
102+
}

‎slack/readme.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
This folder relates to Slack things.
2+
3+
The things:
4+
5+
`greeting`: A text file containing the greeting sent to users who join our Slack server.
6+
7+
`other channels`: A text file containing info on some of our Slack server's channels.
8+
9+
`greeting.slackworkflow`: A workflow exported from Slack for the greeting message. It can be imported should we somehow loose it. Given the format and specific token requirements, it doesn't make sense to maintain the greeting message in this file. Consider it a reference and backup. Maintain in the `greeting` text file and manually update Slack on change.
10+
11+
We could later manage this by creating our own Slack bot, but using Workflows will do for now.
12+
13+
We needed to migrate from Greetbot because they are [shutting down](https://medium.com/greetbot-blog/after-5-million-hellos-its-time-to-say-goodbye-8b82e40b5701).

0 commit comments

Comments
 (0)