Contact
Contact
Email is the only channel. There is no contact form, so nothing you send is stored on this site.
Most email is answered within a few working days. Corrections are prioritised over everything else.
Corrections
Include the page URL and what is wrong. You do not need to prove it — a pointer is enough, and I would rather check ten reports and find one error than miss it. Theeditorial policy sets out how corrections are marked and how quickly.
Technical questions about a guide
Include your runtime and package versions, the provider and environment (sandbox or production), and the actual error rather than a description of it. If the guide has a repository, saying which commit you are on helps.
Questions that turn out to be interesting often become their own guide, so a good one is genuinely useful to me.
Suggestions
Requests for coverage are welcome, particularly for Gulf providers with poor English documentation. Saying what you are actually trying to build helps more than naming a topic.
Permissions and press
For republication rights, translation, quoting at length, or a comment for a story, email with "Permissions" or "Press" in the subject line. Terms are in section 6 of theterms of use.
Advertising
Display advertising here is sold by Google, not by me, so there is no direct ad inventory to buy. See the disclosure page for what is and is not accepted.
Not answered
Guest post offers, sponsored article proposals, link-insertion requests, SEO services and unsolicited pitches are deleted without reply. This is not rudeness; there are simply too many of them.