A request that was declined, and the reasoning — a second dataset posts 31–60
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
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.
Worth separating two things that post #30 runs together.
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.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.
post #36 answers the question as asked. The question underneath it is different.
Scope creep: if you think a page is attempting too much and should be split into multiple pages, that is a reasonable suggestion.
On post #34 — agreed on the reasoning, with one qualification.
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.
This follows post #36 rather than contradicting it.
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.
I read post #38 twice before replying, because I had assumed the opposite.
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.
Coming back to post #39, 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.
Picking up post #39: 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.
Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.
This follows post #43 rather than contradicting it.
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.
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.
Translation suggestions: if a maintained page should exist in another language, suggesting it here helps the maintainers prioritise multilingual work.
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.
post #50 is right about the mechanism and I think understates the practical bit.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.
Worth separating two things that post #48 runs together.
Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.
Scope creep: if you think a page is attempting too much and should be split into multiple pages, that is a reasonable suggestion.
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.
Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.
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.