Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Write a full DevRel program plan for a developer-tool/API company. Deliver: (1) STRATEGY — what DevRel is for here (mapped to a business goal), the developer funnel (awareness->activation->retention->advocacy), and where you'd invest across content, events, community, and DX (avoiding 'random acts of DevRel'); (2) DEVELOPER EXPERIENCE — a docs plan using the Diátaxis four types correctly, maintained sample code/SDK strategy, and an ONBOARDING plan that drives down time-to-first-success and instruments the activation funnel; (3) the PRODUCT FEEDBACK LOOP — how you'd systematically capture developer pain and channel it to product/eng with credibility; and (4) MEASUREMENT — a metrics framework that honestly handles DevRel's hard-to-attribute ROI, uses something like the Orbit model (reach/gravity/love), and explicitly separates VANITY metrics (followers, stars) from meaningful ones (activation, retention, sentiment), with how you'd make the case to leadership. Note the ethics: credibility above metrics, never deceive developers.
DevRel purpose tied to a business goal; funnel-based investment across content/events/community/DX; not random acts.
Docs use Diátaxis correctly; maintained samples; onboarding drives time-to-first-success; a real product-feedback loop with credibility.
Handles hard-to-attribute ROI honestly; Orbit-style engagement; vanity vs meaningful metrics separated; ethics (credibility > metrics) stated.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A DevRel strategy & measurement plan ## Goal Write a full DevRel program plan for a developer-tool/API company. Deliver: (1) STRATEGY — what DevRel is for here (mapped to a business goal), the developer funnel (awareness->activation->retention->advocacy), and where you'd invest across content, events, community, and DX (avoiding 'random acts of DevRel'); (2) DEVELOPER EXPERIENCE — a docs plan using the Diátaxis four types correctly, maintained sample code/SDK strategy, and an ONBOARDING plan that drives down time-to-first-success and instruments the activation funnel; (3) the PRODUCT FEEDBACK LOOP — how you'd systematically capture developer pain and channel it to product/eng with credibility; and (4) MEASUREMENT — a metrics framework that honestly handles DevRel's hard-to-attribute ROI, uses something like the Orbit model (reach/gravity/love), and explicitly separates VANITY metrics (followers, stars) from meaningful ones (activation, retention, sentiment), with how you'd make the case to leadership. Note the ethics: credibility above metrics, never deceive developers. ## Acceptance criteria - [ ] Strategy & alignment: DevRel purpose tied to a business goal; funnel-based investment across content/events/community/DX; not random acts. - [ ] DX & feedback loop: Docs use Diátaxis correctly; maintained samples; onboarding drives time-to-first-success; a real product-feedback loop with credibility. - [ ] Measurement honesty: Handles hard-to-attribute ROI honestly; Orbit-style engagement; vanity vs meaningful metrics separated; ethics (credibility > metrics) stated. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.