# Developer Relations [Developer relations - Wikipedia](https://en.wikipedia.org/wiki/Developer_relations) **Developer relations**, abbreviated as **DevRel**,[1](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:3-1) is an umbrella term for practices employed by an organization that builds developer-facing software to connect with the [developers](https://en.wikipedia.org/wiki/Software_development "Software development") that use that software.[2](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:2-2)[3](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:1-3)[4](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:9-4) Developer relations is a form of [platform evangelism](https://en.wikipedia.org/wiki/Platform_evangelism "Platform evangelism") and the activities involved are sometimes referred to as a developer program or a DevRel program.[3](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:1-3)[5](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:7-5) DevRel programs often include the following:[3](https://en.wikipedia.org/wiki/Developer_relations#cite_note-:1-3) - Developer marketing: Outreach and engagement activities to create awareness and encourage developers to use a product. - Developer education: Product documentation and resources such as videos to aid learning a product. - [[Developer Experience]]: Often referred to as "zeroth customer" and "friction logging", devrel programs include using the product directly, finding problems, and improving the developer experience. - Developer success: Activities to nurture and retain developers as they build and scale with a product. - Community: Events, forums, and social groups around the product.