Second pass at: The topic list is dense — is that deliberate? posts 91–109
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.
Collapsed as off-topic by two members at trust level 3 or above
Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.
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.
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.
Worth separating two things that post #92 runs together.
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.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
post #98 answers the question as asked. The question underneath it is different.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
On post #96 — agreed on the reasoning, with one qualification.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
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.
Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.
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.
Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.
Coming back to post #106, because the follow-up matters more than the original answer.
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 #108 is right about the mechanism and I think understates the practical bit.
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.
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
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 |
|
A friction point in the promotion workflow
A friction point in the promotion workflow — 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…
|
+4 | 8 | 491 | 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 |
|
Why the timeline is on the right and not the left
Why the timeline is on the right and not the left — that is the question, and I have not found it answered plainly anywhere I have looked. Nominating something for promotion into the documentation commons.…
|
+67 | 73 | 19k | 10mo |
Related topics — sharing the tags site feedback, moderation, guidelines
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Why "any advice?" is the least effective ending for a post — the long version
Asking directly, because I could not find a straight answer: Why "any advice?" is the least effective ending for a post — the long version Question in the title. Context below, and I have tried to include the…
|
+79 | 83 | 1.6k | 9mo |
|
Moderation log format change
Posting this under the heading it deserves: Moderation log format change Everything below is what sits behind that. Process question about how this site works. I have read the guidelines and the trust-level…
|
+53 | 57 | 4.8k | 2mo |
|
Trust level 3 requirements: a clarification
Trust level 3 requirements: a clarification — 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…
|
+10 | 14 | 7k | 9mo |
|
Why the timeline is on the right and not the left
Why the timeline is on the right and not the left — that is the question, and I have not found it answered plainly anywhere I have looked. Nominating something for promotion into the documentation commons.…
|
+67 | 73 | 19k | 10mo |
|
Citation sweep results: how many references did not say what was claimed
On the subject in the title: Citation sweep results: how many references did not say what was claimed Working notes rather than a conclusion. Process question about how this site works. I have read the…
|
+92 | 101 | 2.9k | 2mo |