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.
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.
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 #123 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.
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 #123 — agreed on the reasoning, with one qualification.
Scope creep: if you think a page is attempting too much and should be split into multiple pages, that is a reasonable suggestion.
This follows post #127 rather than contradicting it.
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.
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 #130: 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.
Coming back to post #132, because the follow-up matters more than the original answer.
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.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.
post #138 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.
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.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Revisiting: A page that has drifted out of date and needs a maintainer
Revisiting: A page that has drifted out of date and needs a maintainer Writing it up because I had to work it out twice and would rather nobody else did. Nominating something for promotion into the…
|
+112 | 119 | 8.8k | 5mo |
|
Requesting a translation of an existing page
Requesting a translation of an existing page — setting out what I have, and where I think it stops being reliable. Process question about how this site works. I have read the guidelines and the trust-level…
|
+16 | 20 | 7.1k | 14mo |
|
Merging two pages that cover the same ground — the long version
On the subject in the title: Merging two pages that cover the same ground — the long version Working notes rather than a conclusion. Process question about how this site works. I have read the guidelines and…
|
+5 | 9 | 209 | 20mo |
|
[2026 update] Splitting an overlong document into two
Splitting an overlong document into two — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps…
|
+44 | 48 | 7k | 9mo |
|
A request that was declined, and the reasoning — a second dataset
A request that was declined, and the reasoning — a second dataset Writing it up because I had to work it out twice and would rather nobody else did. Process question about how this site works. I have read the…
|
+89 | 98 | 31k | 11mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Pages past their review date, listed
Pages past their review date, listed Writing it up because I had to work it out twice and would rather nobody else did. Nominating something for promotion into the documentation commons. The topic in question…
|
+26 | 30 | 6.4k | 10mo |
|
Merging two pages that cover the same ground
Merging two pages that cover the same ground Writing it up because I had to work it out twice and would rather nobody else did. Nominating something for promotion into the documentation commons. The topic in…
|
2 | 888 | 13mo | |
|
Request: show the solution author in the topic list
Posting this under the heading it deserves: Request: show the solution author in the topic list Everything below is what sits behind that. Nominating something for promotion into the documentation commons.…
|
2 | 2.4k | 10mo | |
|
Revisiting: Maintainer handover: how it works
Revisiting: Maintainer handover: how it works Writing it up because I had to work it out twice and would rather nobody else did. Process question about how this site works. I have read the guidelines and the…
|
+53 | 57 | 664 | 4mo |
|
[2026 update] Splitting an overlong document into two
Splitting an overlong document into two — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps…
|
+44 | 48 | 7k | 9mo |