Handbook components

Reusable components help chapters feel like a practical field guide while keeping authoring Markdown-first. These components are available in every MDX page without imports.

Principle

Name the job before naming the tactic

DevRel work is easier to prioritize when every activity points back to the business and developer job it serves.

<Principle title="Name the job before naming the tactic">
DevRel work is easier to prioritize when every activity points back to the business and developer job it serves.
</Principle>

Practice

Turn field notes into reusable assets

After a launch, collect repeated developer questions and convert them into docs, samples, talks, or product feedback.

<Practice title="Turn field notes into reusable assets">
After a launch, collect repeated developer questions and convert them into docs, samples, talks, or product feedback.
</Practice>

Example

A useful signal loop

A workshop reveals that setup takes too long. The DevRel team writes a clearer quickstart, files product friction, and measures whether future attendees finish faster.

<Example title="A useful signal loop">
A workshop reveals that setup takes too long. The DevRel team writes a clearer quickstart, files product friction, and measures whether future attendees finish faster.
</Example>

Checklist

Before publishing a chapter

The page has one clear thesis.
Examples are concrete enough to reuse.
The next action is obvious.

<Checklist
  title="Before publishing a chapter"
  items={[
    'The page has one clear thesis.',
    'Examples are concrete enough to reuse.',
    'The next action is obvious.',
  ]}
/>

Anti-pattern

Counting motion instead of impact

Publishing more posts, talks, or events is not automatically progress. Measure whether the work changed developer understanding, product quality, community health, or business outcomes.

<AntiPattern title="Counting motion instead of impact">
Publishing more posts, talks, or events is not automatically progress.
</AntiPattern>

Framework

DevRel operating loop

ListenCapture developer needs, objections, and repeated friction.
TranslateTurn signal into content, product feedback, and community action.
MeasureCheck whether the work improved outcomes that matter.

<Framework
  title="DevRel operating loop"
  steps={[
    {label: 'Listen', description: 'Capture developer needs, objections, and repeated friction.'},
    {label: 'Translate', description: 'Turn signal into content, product feedback, and community action.'},
    {label: 'Measure', description: 'Check whether the work improved outcomes that matter.'},
  ]}
/>

Reflection prompt

<ReflectionPrompt question="What developer behavior should change after this chapter?">
Write the answer before drafting the page.
</ReflectionPrompt>

Principle​

Name the job before naming the tactic

Practice​