Hey there Devrel Friends!
Devrel Notebook is a repo that holds a lot of information in a form of notes. hose notes were taken reading / listening or watching various resources and may lack original authors of the thoughts. We're open for Pull Requests to add those! Happy learning!
In this repo you will be able to gain knowledge about various fields of the Developer Relations umbrella like:
but also read some more or less loose notes. Let us walk you into the Developer Relations world!
Developer Relations is about building trust at scale. Before you start diving into this repo we just want you to remember one thing: Developer Relations is a JOB AND NOT a LIFESTYLE. Don't be mislead by all those DevRel people constantly tweeting. Although charisma can be faked, DevRel requires genuine enthusiasm for your platform or product, so let's start learning!
Developer Relations is about:
- Outreach (online and in person)
- Community
- Product
- Education and support
Developer Relations Funnel
In order to be able to do solid DevRel, you need to fulfill certain needs of your developer audience that can be divided into folllowing categories:
- Basic Needs
- Psychological Needs
- Self-fulfillment
All of those are shown on the figure below:
Developer Relations Core Elements:
- Awareness - awareness of the platform and what it does
- Acquisition - sign-up/download/install
- Activation - actively using the platform in an application
- Retention - continue to use the platform, use of new/additional features and use in new apps
- Revenue - pay to use the platform
- Referral - tell others about the platform
- Product - involvement in building and getting feedback on product
DevRel Team
Here are some notes on building successful DevRel Teams. There are three key roles that you need in your DevRel team:
-
The Evangelist
-
Just as the name suggests, these are the people who stand on stages and preach to thousands of developers about a particular tool or product that makes building software worthwhile. They are the PR face of the company and attend various conferences and meetups to share information about a product, collect first-hand feedback and show off killer slides with memes.
-
The Facilitator / Educator
-
Developers need the materials behind your product – from documentation to quick start guides. This is what facilitators and educators do; they provide the backbone support for developers to enable them to find their way around your product. You’ll also find them running technical training events and speaking at workshops and meetups. They may not be the most outgoing of the bunch but their product knowledge and knack for making complex topics digestible is priceless.
-
The Organiser
-
They act as fuel to the community that you’re building around your product – maintaining peace and prosperity in the community, making sure that any issues raised are sorted out ASAP and rewarding the various great people in the community for their contributions.
Have that in the back of your head: Developer Relations is hard to measure, subjective and time-intensive