Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.
Search filters: what is missing posts 61–85
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Worth separating two things that post #59 runs together.
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.
post #63 is right about the mechanism and I think understates the practical bit.
Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.
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.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
post #67 answers the question as asked. The question underneath it is different.
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).
Moderation decisions: if you disagree with a moderation decision, raising it here gives it visibility. Staff will reconsider if you make a substantive case.
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.
Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.
Picking up post #70: that is the part I would want checked first.
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.
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.
This follows post #74 rather than contradicting it.
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).
I read post #76 twice before replying, because I had assumed the opposite.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
post #78 answers the question as asked. The question underneath it is different.
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.
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.
Coming back to post #81, because the follow-up matters more than the original answer.
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.
Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.
This topic was referenced in
- Why the timeline is on the right and not the leftMeta › Site feedback · 73 replies
- Follow-up: The topic list is dense — is that deliberate?Meta › Site feedback · 4 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Tag proliferation and whether we should prune
On the subject in the title: Tag proliferation and whether we should prune Working notes rather than a conclusion. Process question about how this site works. I have read the guidelines and the trust-level…
|
2 | 11k | 11mo | |
|
The topic list is dense — is that deliberate?
The topic list is dense — is that deliberate? — that is the question, and I have not found it answered plainly anywhere I have looked. Nominating something for promotion into the documentation commons. The…
|
+83 | 91 | 49k | 18mo |
|
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 |
|
Tag proliferation and whether we should prune — what changed since
Tag proliferation and whether we should prune — what changed since — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The…
|
+5 | 9 | 709 | 5mo |
|
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 |
Related topics — sharing the tags site feedback, moderation, guidelines
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Pages past their review date, listed — does this still hold?
Asking directly, because I could not find a straight answer: Pages past their review date, listed — does this still hold? Nominating something for promotion into the documentation commons. The topic in…
|
+49 | 56 | 39k | 11d |
|
Follow-up: Request: a per-category review queue
On the subject in the title: Request: a per-category review queue Working notes rather than a conclusion. Nominating something for promotion into the documentation commons. The topic in question keeps being…
|
2 | 14k | 4mo | |
|
Five questions in one post gets you one answer — how to split them
On the subject in the title: Five questions in one post gets you one answer — how to split them Working notes rather than a conclusion. Question in the title. Context below, and I have tried to include the…
|
+84 | 90 | 1k | 2mo |
|
Coming back to: A community side-effect dataset, with its response rate and biases
Posting this under the heading it deserves: A community side-effect dataset, with its response rate and biases Everything below is what sits behind that. Working through the identity arithmetic and I would…
|
+96 | 101 | 33k | 2d |
|
Request: export my own posts — one year on
Request: export my own posts — one year on — 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…
|
+66 | 70 | 14k | 4mo |