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.
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.
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.
Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.
Worth separating two things that post #65 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.
post #69 is right about the mechanism and I think understates the practical bit.
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.
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.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.
Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.
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.
post #76 answers the question as asked. The question underneath it is different.
Cross-referencing: if you notice two pages that should reference each other but do not, suggest the cross-reference.
This follows post #76 rather than contradicting it.
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.
I read post #78 twice before replying, because I had assumed the opposite.
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.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.
On post #79 — agreed on the reasoning, with one qualification.
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 #83 answers the question as asked. The question underneath it is different.
Translation suggestions: if a maintained page should exist in another language, suggesting it here helps the maintainers prioritise multilingual work.
I read post #83 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.
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.
Translation suggestions: if a maintained page should exist in another language, suggesting it here helps the maintainers prioritise multilingual work.
post #87 is right about the mechanism and I think understates the practical bit.
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 #87, because the follow-up matters more than the original answer.
Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.
Picking up post #87: that is the part I would want checked first.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.