https://github.com/fharper/devrel
Multiple resources & information for developer relations
https://github.com/fharper/devrel
developer-relations devrel resources tools
Last synced: 6 months ago
JSON representation
Multiple resources & information for developer relations
- Host: GitHub
- URL: https://github.com/fharper/devrel
- Owner: fharper
- License: unlicense
- Created: 2022-08-20T17:35:06.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-06-26T18:46:20.000Z (almost 2 years ago)
- Last Synced: 2025-04-02T23:51:25.495Z (12 months ago)
- Topics: developer-relations, devrel, resources, tools
- Language: Shell
- Homepage:
- Size: 21.3 MB
- Stars: 4
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Developer Relations
[](https://github.com/fharper/devrel/actions/workflows/check-markdown.yml) [](https://github.com/fharper/devrel/actions/workflows/check-links.yml)
This repository serves as a second brain for my work in Developer Relations (devrel).
I will slowly add our processes, ideas, and everything needed to be successful with devrel. It's a work-in-progress, but I firmly believe other companies, or individual contributor, could benefit from my expertise and experience of doing developer relations.
As always, we value constructive feedback. Welcome home!
## Table of content
- [Communities](resources/devrel.md#communities)
- [Developer Relations 3Cs](#the-3cs)
- [Developer Relations Mission](#my-mission)
- [Developer Relations Resources](resources/devrel.md)
- [Jobs/Roles Information](jobs/README.md)
- [Onboarding](onboarding/onboarding.md)
- [Ownership](devrel/ownership.md)
- [Scripts](scripts/README.md)
- [Writing Guidelines](content/writing/README.md)
## Developer Relations
### My Mission
I help developers be successful by nurturing a healthy and welcoming community around my employer ecosystem. This means listening to, advocating for, inspiring, educating, and supporting our community however I can.
### The 3Cs
The three pillars of Developer Relations are **C**ommunity, **C**ontent, and **C**ode, also known as the 3Cs*.
The main focus of our team is the community: just read our mission to understand that everything we do is for our developer community. To help us achieve our mission, we use two main activities: content and code. The former is any type of content on any useful medium; some examples are talks at conferences, the developer documentation, or video tutorials. The latter, code, is part of the foundation of who we are: we are developers. It translates into code examples for the documentation, code demos for our conference presentations, technical support, demo applications, or even being responsible for specific APIs or contributing to open source to give back to the community and be a good web citizen. All together, they form the foundation of developer relations.
\* _adapted from [SendGrid 2014 article](https://sendgrid.com/blog/3-cs-developer-relations/)_