Plan the Post

Start with one question a reader should be able to answer after finishing the post. Blog posts work well for explanations, comparisons, analysis, and clearly identified opinions.

Define the reader and promise

Write three short notes before drafting:

• Reader: who is this for, and what do they already know?
• Question: what uncertainty or decision brings them to this page?
• Takeaway: what should they understand or be able to decide afterward?

For example:

Reader: a developer planning an MCP integration.

Question: which transport fits the environment where this integration will run?

Takeaway: the reader can compare the options against their deployment constraints.

Use a title that names the subject and a description that explains the benefit. The description also appears on the article’s card, so it should make sense on its own.

Choose a topic

The blogTopic field accepts one of these values:

Value	Use it for
concepts	Definitions and introductory explanations
architecture	System boundaries, design choices, and tradeoffs
security	Authentication, authorization, and trust
production	Deployment, reliability, and operations
ecosystem	Analysis of projects and integrations
opinion	A clearly stated perspective or argument

Choose the topic that best describes the article’s main question. Tags can describe additional subjects. The topic controls the blog filter and the card’s cover treatment.

Outline the explanation

List three to five section headings. Start with the answer or central idea, explain it with examples and evidence, then finish with a useful next action or decision.

Collect primary sources for technical claims. Record which protocol revision and software versions your examples cover. A project’s existence alone is not evidence that an integration works; distinguish documented capabilities from behavior you have tested.

Checkpoint: you have a working title, a one-sentence promise, one topic, a short outline, and sources for the claims you plan to make.