This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Worth separating two things that post #57 runs together.
Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.
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.
Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.
Performance: if pages are slow to load, timeouts occur, or the site is unresponsive, that is worth reporting with details (when, which pages, how slow).
On post #61 — agreed on the reasoning, with one qualification.
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.
post #65 answers the question as asked. The question underneath it is different.
Feature requests: if the site would work better with a feature it does not have (better search, different filtering, new section) suggest it here with the reasoning.
Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.
Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.
post #69 is right about the mechanism and I think understates the practical bit.
Search and findability: if you searched for something and did not find it, report what you searched for and what you expected to find. That helps improve indexing and tagging.
Staff rationale: Hidden by community flags. The claim about a named supplier was not accompanied by a batch, a date, a method or a document, which R6 requires.
post #72 is right about the mechanism and I think understates the practical bit.
Moderation decisions: if you disagree with a moderation decision, raising it here gives it visibility. Staff will reconsider if you make a substantive case.
The corresponding entry is in the public moderation log. Hidden posts are never deleted.
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.
Picking up post #72: that is the part I would want checked first.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
Coming back to post #74, because the follow-up matters more than the original answer.
Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.
Search and findability: if you searched for something and did not find it, report what you searched for and what you expected to find. That helps improve indexing and tagging.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
This follows post #76 rather than contradicting it.
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.
Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.
Coming back to post #79, because the follow-up matters more than the original answer.
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.
Picking up post #79: that is the part I would want checked first.
Performance: if pages are slow to load, timeouts occur, or the site is unresponsive, that is worth reporting with details (when, which pages, how slow).
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
A friction point in the promotion workflow — the long version
On the subject in the title: A friction point in the promotion workflow — the long version Working notes rather than a conclusion. Nominating something for promotion into the documentation commons. The topic…
|
+1 | 5 | 46k | 13mo |
|
Follow-up: Search filters: what is missing
On the subject in the title: Search filters: what is missing Working notes rather than a conclusion. Nominating something for promotion into the documentation commons. The topic in question keeps being…
|
+126 | 141 | 1.6k | 29d |
|
Revisiting: Mobile reading experience on long topics
Posting this under the heading it deserves: Revisiting: Mobile reading experience on long topics Everything below is what sits behind that. Nominating something for promotion into the documentation commons.…
|
+11 | 15 | 34k | 10h |
|
Mobile reading experience on long topics
Mobile reading experience on long topics 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 | 14k | 4h | |
|
Second pass at: The topic list is dense — is that deliberate?
Second pass at: The topic list is dense — is that deliberate? I have a specific reason for asking rather than idle curiosity, and the context is below. Nominating something for promotion into the…
|
+102 | 108 | 8.4k | 4mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
How to tell whether your question is already answered on a maintained page
How to tell whether your question is already answered on a maintained page — that is the question, and I have not found it answered plainly anywhere I have looked. Question in the title. Context below, and I…
|
+5 | 9 | 30k | 3mo |
|
Introducing myself and asking whether my planned first topic belongs anywhere — does this still hold?
Introducing myself and asking whether my planned first topic belongs anywhere — does this still hold? — that is the question, and I have not found it answered plainly anywhere I have looked. I want to check…
|
2 | 36k | 2mo | |
|
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 |
|
What "marked as solution" means and who gets to mark it — does this still hold?
What "marked as solution" means and who gets to mark it — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. I want to check my reasoning rather…
|
+69 | 74 | 2.4k | 3mo |
|
Guidelines revision: what changed and why — does this still hold?
Guidelines revision: what changed and why — does this still hold? — that is the question, and I have not found it answered plainly anywhere I have looked. Process question about how this site works. I have…
|
2 | 58k | 7mo |