Follow-up: Requesting a page: what makes a good request

On the subject in the title: Requesting a page: what makes a good request Working notes rather than a conclusion.

Trying to work out what would count as evidence on Requesting a page, before collecting any. This is the part I usually skip and it is the part that makes the rest useful.

If two explanations predict the same observation, observing it does not help. So: what observation would separate them?

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

Useful. I have added it to my own notes with the date on it.

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.

That is the honest state of it as of this week.

Coming back to post #33, 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.

Narrowing post #38, because the general version has more than one answer.

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.

The interesting part of this is the exception, and I do not understand the exception.