Requesting a page: what makes a good request — what changed since posts 31–60

Flag a page that has drifted: if you notice a maintained page has information that is outdated (dates that have passed, regulatory changes, new evidence) post a flag so the maintainers see it.

Two things before anyone answers the substance.

First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.

Picking up post #44: that is the part I would want checked first.

Correction requests: if you spot an error in a maintained page, note it here with the specific correction. The maintainer will review and update if justified.

Coming back to post #46, because the follow-up matters more than the original answer.

Translation suggestions: if a maintained page should exist in another language, suggesting it here helps the maintainers prioritise multilingual work.

post #48 is right about the mechanism and I think understates the practical bit.

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

Worth separating two things that post #46 runs together.

Request a new maintained page: if a question recurs, has a good marked solution, and contains a worked example, it is a candidate for promotion to a maintained documentation page. Post your nomination in this subcategory with a link to the topic.

Suggesting content for a page: if you know a maintained page is missing something important, post a suggestion with specific content you think should be added.

Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.

On post #49 — agreed on the reasoning, with one qualification.

Translation suggestions: if a maintained page should exist in another language, suggesting it here helps the maintainers prioritise multilingual work.

post #53 answers the question as asked. The question underneath it is different.

Correction requests: if you spot an error in a maintained page, note it here with the specific correction. The maintainer will review and update if justified.

I read post #53 twice before replying, because I had assumed the opposite.

Suggesting content for a page: if you know a maintained page is missing something important, post a suggestion with specific content you think should be added.

Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.

Request a new maintained page: if a question recurs, has a good marked solution, and contains a worked example, it is a candidate for promotion to a maintained documentation page. Post your nomination in this subcategory with a link to the topic.

post #57 is right about the mechanism and I think understates the practical bit.

Authority and authorship: if you think a maintained page needs input from someone with specific expertise (a clinician, an analytical chemist) suggest who might contribute.

Coming back to post #57, because the follow-up matters more than the original answer.

Having read the exchange above, I think I was wrong earlier in this topic and I want to say so plainly rather than quietly editing.

The correction was fair and I had been repeating something I had not checked carefully enough.

Picking up post #57: that is the part I would want checked first.

Cross-referencing: if you notice two pages that should reference each other but do not, suggest the cross-reference.