One answer per article, self-contained, titled as the question somebody would type. Fill in the question and summary fields — they are what search and the assistant use, and a summary sliced off the body is not an answer.

The Knowledge Base has three fields that look redundant and are not: the title, the question and the summary.

The title is short, for a sidebar. The question is what somebody would actually type — "Why does my logo not appear?" finds things that "Branding" does not. The summary is a written two-sentence answer.

🚨 The summary must be written rather than the opening of the article. It is what gets quoted when the whole article is too long to show, and the first sentence of a piece of writing is a sentence that happened to be first — not an answer.

One answer per article, and make each one stand alone. An article that only makes sense after the four before it is useless when it arrives on its own next to two unrelated ones, which is exactly how a search result and an assistant answer arrive.

Set the audience — everyone, members, administrators or developers — so people are not reading documentation written for somebody else.

Sign in to say whether this helped.