{"id":22381212,"url":"https://github.com/episod/developer-relations-template","last_synced_at":"2026-02-07T17:04:42.958Z","repository":{"id":201094062,"uuid":"706430881","full_name":"episod/developer-relations-template","owner":"episod","description":"A template for starting or restarting developer relations programs","archived":false,"fork":false,"pushed_at":"2023-11-17T22:33:07.000Z","size":845,"stargazers_count":7,"open_issues_count":0,"forks_count":1,"subscribers_count":4,"default_branch":"main","last_synced_at":"2025-07-12T03:20:18.136Z","etag":null,"topics":["devrel","devrel-teams","platform-products"],"latest_commit_sha":null,"homepage":"https://devrel.realitytechnicians.com","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"cc-by-4.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/episod.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-10-18T00:03:17.000Z","updated_at":"2024-09-12T05:34:15.000Z","dependencies_parsed_at":"2023-11-14T01:27:20.249Z","dependency_job_id":"2092af18-97db-4af2-accb-f524a735e426","html_url":"https://github.com/episod/developer-relations-template","commit_stats":null,"previous_names":["episod/developer-relations-template"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/episod/developer-relations-template","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/episod%2Fdeveloper-relations-template","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/episod%2Fdeveloper-relations-template/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/episod%2Fdeveloper-relations-template/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/episod%2Fdeveloper-relations-template/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/episod","download_url":"https://codeload.github.com/episod/developer-relations-template/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/episod%2Fdeveloper-relations-template/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29200843,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-07T16:28:23.579Z","status":"ssl_error","status_checked_at":"2026-02-07T16:28:22.566Z","response_time":63,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["devrel","devrel-teams","platform-products"],"created_at":"2024-12-05T00:07:52.198Z","updated_at":"2026-02-07T17:04:42.941Z","avatar_url":"https://github.com/episod.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"---\ntitle: About the DevRel anywhere template\ndescription: Learn how the developer relations anywhere template can help start or restart a devrel function.\n---\n\n# How to use the \"developer relations anywhere\" template\n\nThis is a adaptable template to build [draft developer relations plans](template.md) when starting or restarting developer relations programs.\n\nOne way to use this template is to organize your understanding of an organization's needs during the interview process. You can remove what's not relevant to their goals, add your hunches and analysis as they develop.\n\nThis template can then translate well in developing your plans over the next several months and years as your developer ecosystem matures.\n\nI've been extraordinarily lucky to work in the early days of technical evangelism, developer relations, and platform management at a number of companies and this template represents my approach to tackling _developer relations anywhere_.\n\n---\n\n## How to use this\n\nThis [draft developer plan](template.md) is a template meant to be cloned for your own organization. \n\nThe draft references abstract _platform product_ and treats _developers_ as a very broad category. \n\nIn reality, your product is more specific and you likely have a subset of the entire developer market in mind. _Bring your own platform facts, foibles, and fun._\n\nThis template is most effective for growth-minded developer relations teams operating directly with product and engineering. Suggested local metrics are mostly placeholders, meant to be replaced with the kinds of metrics you care about.\n\nCustomize the template as you learn about your company, its platform, and its developers. Find the approach that will serve them best by removing irrelevant subteams or adding new ones.\n\n**Suggestions or improvements welcome**. This belongs to all of us!\n\n## Customization suggestions\n\n### Team structure\n\nIf your team is just starting out and it's only you, use this section to help guide and divide the work your team of one has to accomplish. Maybe you don't have partners yet and don't need to help them hands-on. Maybe your company is already setup to serve developers well with their own documentation or tools team.\n\nAll these categories are your responsibility in developer relations whether another team owns the work product around them or not. As you identify your weak spots and how you could better serve your unique developer audience, begin hiring those who can make a major impact in one or more of these specializations.\n\nAs your team grows and each specialization team becomes their own thing, you need to find ways to mix and remix the cross-functional work together. Usually one or more people on the team will emerge as \"operators\" who cross the boundaries of 2 or 3 different teams, contributing to sample apps, documentation, product development, and advocacy all at the same time. Take a penny, leave a quarter kind of work.\n\n### Metrics\n\nDeveloper relations is largely a faith-based operation. You believe that your work is going to make a developer more likely to succeed and that a developer's success is good for your platform.\n\nThat belief, along with empathy, motivates most decisions developer relations teams will make day-to-day. Just as you don't want your team to watch the clock like their work is a form of torture, you also don't want to focus _overmuch_ on trailing metrics you don't have much direct control on.\n\n_Local_ metrics are within direct influence of the developer relations team. You can increase time on page. You can encourage readers through a specific funnel. You can reduce error rates in the CLI. Identifying friction is quantifying friction. Reduced friction is a local metric in developer relations' control and will, with faith, influence developer activation and enablement. Developer relations _can_ drive feature adoption and breadth. Your platform is best when your developer relations team loves it; `XX% of developer relations team agrees X is good` is a measure worth tracking.\n\nFind what is locally relevant for your team.\n\n## Activation\n\nYou want as many developers or visitors to reach an ah-ha moment that convinces them your solution is the right one, provided it is.\n\nFrom that point forward, every piece of friction in their experience can stop them from successfully accomplishing their goal.\n\nReducing friction reduces time to business logic. The joy in programming is there, in the business logic.\n\nBuild a _friction log_ however you see fit, as a collection of observations (\u0026 occasional suggestions) on friction encountered through a developer experience.\n\nThink of it like a journal kept while walking through your platform's metaphorical park. Useful in early stages of joining a developer relations team to introduce an outside perspective. In later stages of team membership, to continue the metaphor, it's important to pick up the easy trash as you go. No use hoarding maps of all the litter in the park.\n\n## Thanks to\n\nThank you to the one who helped with my first Perl ah-ha moment, it's guided the way since. Thank you for the tips, tricks, traps, trouble, and trust Brandon, Jim, Adam, Ryan, Amir, and Bear. Teams are where the dream becomes reality and the teams I work with teach me what's possible and probably at every turn. Thanks to LinkedIn, (the original) Twitter, Clever, and Slack for letting me stumble through devrel origin stories. And thank you to the partners in crime I depend on and learn from all the time.\n\n## Changelog\n\n* November 2023 - continue developing the README.md framing, move to [`https://devrel.realitytechnicians.com/`](https://devrel.realitytechnicians.com/)\n* October 2023 - moved from Google Docs to Github to better enable community collaboration and adaptation. Re-organizing content and content about content.\n* June 2023 - first draft authored by [Taylor Singletary](https://www.realitytechnicians.com) (@episod)\n\n## TODOs\n\n* Add variant templates for different types of developer products (Web APIs, developer tools, databases, etc)\n* Add campaign examples for growth efforts\n\n## License\n\nThis work is licensed under a\n[Creative Commons Attribution-ShareAlike 4.0 International License][cc-by-sa].\n\n[![CC BY-SA 4.0][cc-by-sa-image]][cc-by-sa]\n\n[cc-by-sa]: http://creativecommons.org/licenses/by-sa/4.0/\n[cc-by-sa-image]: https://licensebuttons.net/l/by-sa/4.0/88x31.png\n[cc-by-sa-shield]: https://img.shields.io/badge/License-CC%20BY--SA%204.0-lightgrey.svg\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fepisod%2Fdeveloper-relations-template","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fepisod%2Fdeveloper-relations-template","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fepisod%2Fdeveloper-relations-template/lists"}