All Resend content should read as though written by a developer.
Here are some voice, tone, and language guidelines.
Get to the point and avoid unnecessary complexity, redundancy, and verbal garnish. Our content should not be thinly veiled sales pitches or lazy fluff for the sake of volume.
Use positive assertions that you can provide evidence for. Engineers are on alert for claims they can poke holes in, and once found, their trust in us is shattered.
We expect our audience to feel comfortable reading a fairly technical piece. Including technical details can not only be clarifying, but also make it clear that our content is not just an arm of the marketing function.