# DevRel Documentation (https://devrel.directory/docs)





devrel.directory is an open knowledge base for Developer Relations.
It explains what DevRel is, how the roles differ, and how to build a program that holds up in practice.
The content is written for practitioners, cites its sources, and is free to use.

New to the field? [Start here](/start) instead - a sequenced route in, built from live data: what to read in order, which communities are actually alive, which calls for papers are open now, and what the job market is really hiring for.

## DevRel in the AI era [#devrel-in-the-ai-era]

<Cards>
  <Card icon="<Bot />" title="AI-era DevRel">
    How DevRel changes when developers bring AI agents - the practical guide: [Agents Are Your New Developers](/docs/ai-era/agents-as-your-new-developers).
  </Card>

  <Card icon="<FileText />" title="Writing Docs LLMs Can Use">
    llms.txt, Markdown mirrors, and the structure that makes documentation retrievable and quotable by AI assistants: [Writing Docs LLMs Can Use](/docs/ai-era/docs-for-llms).
  </Card>

  <Card icon="<Server />" title="MCP Servers Are the New SDK">
    Why an MCP server is a DevRel surface, what to expose through it, and the work that makes one succeed: [MCP Servers Are the New SDK](/docs/ai-era/mcp-servers-as-devrel-surface).
  </Card>

  <Card icon="<ChartLine />" title="Measuring Adoption You Cannot See">
    Why classic web analytics undercount AI-driven adoption and what you can measure honestly instead: [Measuring Adoption You Cannot See](/docs/ai-era/measuring-ai-driven-adoption).
  </Card>
</Cards>

## Start with the fundamentals [#start-with-the-fundamentals]

<Cards>
  <Card icon="<Book />" title="Definition of Developer Relations">
    What DevRel is and what it is not, with the research behind the definition: [Definition of Developer Relations](/docs/fundamentals/definition).
  </Card>

  <Card icon="<Lightbulb />" title="The Importance of DevRel">
    Why developer communities compound like network effects and what that means for a business: [The Importance of DevRel](/docs/fundamentals/importance).
  </Card>

  <Card icon="<Users />" title="Roles and Responsibilities">
    Advocate, evangelist, developer experience, developer marketing: how the roles differ and where they overlap: [Roles and Responsibilities](/docs/fundamentals/roles-and-responsibilities).
  </Card>

  <Card icon="<Target />" title="Crafting a DevRel Strategy">
    Objectives, audience, and measurable goals for a DevRel program: [Crafting a DevRel Strategy](/docs/fundamentals/devrel-strategy).
  </Card>

  <Card icon="<Users />" title="Developer Personas">
    How to build research-backed personas instead of guessing who your developers are: [Understanding Developer Personas](/docs/fundamentals/understanding-developer-personas).
  </Card>
</Cards>

## Put it into practice [#put-it-into-practice]

<Cards>
  <Card icon="<ListChecks />" title="DevRel Activities">
    The core activity clusters, when each earns its place, and how to avoid activity soup: [DevRel Activities](/docs/practices/devrel-activities).
  </Card>

  <Card icon="<MessagesSquare />" title="Community Building">
    From the first fifty members to programs that scale, plus behaving well in communities you do not own: [Community Building](/docs/practices/community-building).
  </Card>

  <Card icon="<PenLine />" title="Content Creation">
    Content types, writing craft, distribution, and a pipeline a small team can sustain: [Content Creation](/docs/practices/content-creation).
  </Card>
</Cards>

## What is Developer Relations? [#what-is-developer-relations]

Developer Relations (DevRel) is the function that connects a company and the developers who build with its products.
Done well, it drives adoption, feeds honest feedback back into the product, and builds communities that outlast any single campaign.

<Callout type="info">
  "DevRel is more than just a job title - it's a strategic approach to building and nurturing relationships between companies and developers." - From our [Definition of Developer Relations](/docs/fundamentals/definition)
</Callout>

## More on the site [#more-on-the-site]

<Cards>
  <Card icon="<BookOpen />" title="Blog">
    Longer pieces on strategy and planning live in the [blog](/blog).
  </Card>

  <Card icon="<GalleryVerticalEnd />" title="Changelog">
    What changed on the site and when: [changelog](/changelog).
  </Card>

  <Card icon="<PenLine />" title="Contribute">
    Listings, jobs, events, and docs improvements are all welcome - start with the [contributing guide](/docs/additional-resources/contributing).
  </Card>
</Cards>

## This knowledge base is growing [#this-knowledge-base-is-growing]

The docs are being reworked and expanded section by section.
If a topic you need is missing or a page falls short, send a correction or a suggestion - the [contributing guide](/docs/additional-resources/contributing) explains how.