@@ -196,8 +196,8 @@ We use Slack internally as a communication tool. The Marketing channels are as f
Automated channels with feeds from different sources:
-`#developer-advocacy-updates`: [Zapier workflows](/handbook/marketing/developer-relations/workflows-tools/zapier/) automatically post GitLab blog posts, Developer Relations social shares, competitive insights, Common Room updates, etc.
-`hn-mentions`: Hacker News post feed, automated with [Zapier](/handbook/marketing/developer-relations/workflows-tools/zapier/)and maintained by the Developer Relations team.
-`#developer-advocacy-updates`: [automated workflows](/handbook/marketing/developer-relations/workflows-tools/workato/) to post GitLab blog posts, Developer Relations social shares, competitive insights, Common Room updates, etc.
-`hn-mentions`: Hacker News post feed, automated and maintained by the Developer Relations team.
-`social_media_posts`: Automated social media post feed.
@@ -125,7 +125,7 @@ Please read the [Content](/handbook/marketing/developer-relations/developer-advo
Our team regularly engages with GitLab customers and the wider GitLab community.
The Developer Advocate team is the DRI for questions and strategy on the platforms below:
<!-- This partially duplicates https://handbook.gitlab.com/handbook/marketing/developer-relations/workflows-tools/#tool-stack-overview - when making updates, ensure to keep it in sync. -->
<!-- This partially duplicates https://handbook.gitlab.com/handbook/marketing/developer-relations/workflows-tools/ - when making updates, ensure to keep it in sync. -->
| Platform | Description | Workflows |
|-------------|-------------|-----------|
@@ -174,7 +174,7 @@ Our team maintains projects to provide GitLab use cases for content creation (de
GitLab team members can also reach us at any time on the [#dev-advocacy-team](https://app.slack.com/client/T02592416/CMELFQS4B) Slack channel where we share updates, ideas, and thoughts with each other and the wider team.
We use [developer-advocacy-updates](https://gitlab.slack.com/archives/C04R2RME4F7) for content shares and other updates that don't warrant generating noise in the larger channel. Many updates are automated using [Zapier workflows](/handbook/marketing/developer-relations/workflows-tools/zapier/)
We use [#developer-advocacy-updates](https://gitlab.slack.com/archives/C04R2RME4F7) for content shares and other updates that don't warrant generating noise in the larger channel. Many updates are automated using [Workato workflows](/handbook/marketing/developer-relations/workflows-tools/workato/)
@@ -94,9 +94,7 @@ Blog comments can be easily monitored by filtering forum topics by the [feedback
## Automation
Hacker News mentions of configured keywords for GitLab are monitored using [Zapier](https://zapier.com) workflows.
Hacker News mentions of configured keywords for GitLab are monitored using Slack's [RSS app](https://slack.com/help/articles/218688467-Add-RSS-feeds-to-Slack) and RSS feeds from [https://hnrss.github.io/](https://hnrss.github.io/).
- Keyword mentions are tracked in the [#hn-mentions](https://gitlab.slack.com/messages/hn-mentions) Slack channel.
- Front page notifications are posted into the [#dev-advocacy-team](https://gitlab.slack.com/messages/dev-advocacy-team) Slack channel.
All Zapier workflows with keywords are documented in the [Developer Relations handbook](/handbook/marketing/developer-relations/workflows-tools/zapier/#current-zaps), including details on [how the Algolia Search for Hacker News](/handbook/marketing/developer-relations/workflows-tools/zapier/#zaps-for-hacker-news) is used.
| Crowdin | [Crowdin](https://translate.gitlab.com/) is the platform for the wider community to collaboratively contribute translations for GitLab | [How we use Crowdin](https://docs.gitlab.com/ee/development/i18n/translation.html) |
| Discourse | [Discourse](https://www.discourse.org) is the platform on which the [GitLab forum](https://forum.gitlab.com) is run. | [How we use Discourse](/handbook/marketing/developer-relations/workflows-tools/forum/#administration)|
| Discord | [Discord](https://discord.gg/gitlab) is the instant messaging platform the GitLab community communicates on (in addition to GitLab.com itself) | popular channels are #contribute, #general and the support channels |
| Proxi.id | [Proxi.id](https://www.proxi.id/) is the platform we use to automatically qualify applications for our community programs | |
| Zapier | [Zapier](https://zapier.com) is an automation tool used to identify mentions and to route them into Zendesk as tickets, and also to Slack in some cases | [How we use Zapier](/handbook/marketing/developer-relations/workflows-tools/zapier) |
</details>
### Tools pending addition to tech stack
The Developer Relations team is also the DRI for these tools, which are pending addition to the Tech Stack through the HelpLab [Tech Stack Update](https://helplab.gitlab.systems/esc?id=sc_cat_item&sys_id=7eee5c19ff25e6503691fe34fc4fd9ab) process:
@@ -89,4 +59,3 @@ These are the tools that are essential to some Community programs, but the Devel
### Adding a new tool to the Developer Relations tool stack
1. Please follow the procurement process as you would when adding any new tool through the HelpLab [Tech Stack Update](https://helplab.gitlab.systems/esc?id=sc_cat_item&sys_id=7eee5c19ff25e6503691fe34fc4fd9ab) process.
1. Ensure that the `group_owner` field on the tech stack file entry is set to `Developer Relations`. This will make the tool to be automatically listed on the [Developer Relations toolstack](#tool-stack-overview).
