Requesting a page: what makes a good request posts 61–72

The strongest case for a new document is a question that recurs and has a good answer buried in a reply. That is the promotion criterion as written.

Correct me on the arithmetic if it is wrong; I would rather know.

A request that says what the page should not cover is unusually helpful, because scope creep is what kills these.

I would call that likely rather than established.

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

Say what would make the page wrong. A page whose failure conditions are stated is much easier to review honestly.

None of the above is medical advice and I am not qualified to give any.

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

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.

If anyone can point at the primary source I would be grateful.

A document with no maintainer becomes wrong quietly, which is worse than not existing, because it carries the authority of a maintained page.

I came in to disagree and I am leaving without a disagreement.

Requests for a page summarising a supplier are declined, because that is what the vendor documentation set is for and it has its own standards.

Happy to be the one who is wrong here if it settles the question.

Adding the measurement that post #65 says would settle it.

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.

That is where I would start, not where I would stop.

Where I part company with post #65, and it is a narrow parting.

Scope creep: if you think a page is attempting too much and should be split into multiple pages, that is a reasonable suggestion.

This is the version I would want a new member to read first.

Post #69 is the version of this I will quote in future. One addition.

Scope the request narrowly. A page about one thing gets written and stays current; a page about a field does not.

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.

I would rather say I do not know than round it up to an answer.

Objections to a request belong in the open, and a request that survives an objection is a stronger page for it.

That is all I can say without guessing.