blog-writing-guide

Start with the problem or conclusion in the first two sentences, then structure the post around reader questions: what problem it solves, how it works technically, trade-offs considered, and how to try it. Apply the Sentry voice and avoid banned marketing phrases.

Run two checklists: a technical review verifying claims, working code, and accurate numbers, plus an editorial review checking the opening hook, informative headings, title strength, and the "would I share this?" test. Quote weak passages and rewrite them as examples.

Avoid corporate filler like "we're excited to announce", "seamless", "best-in-class", "leverage", "robust", and "streamline". Also avoid AI writing tells such as staccato dramatic fragments, bumper-sticker aphorisms, and three-beat reveals.

Yes. It recommends leading with tool-agnostic educational content, putting keywords in H2 headings, including a definitional "What is X?" section, and adding an FAQ targeting long-tail keywords for featured snippets.

A style guide enforces voice, structure, and editorial standards but cannot verify that code samples actually run or that performance numbers are accurate. Authors must still test code and confirm technical claims with the engineers who built the system.