Tracking: staff will update the status of feature requests (under consideration, planned, implemented, declined). Checking back lets you know the fate of your suggestion.
2 likes 6d
Meta · Feature requests · continued
Request: a per-category review queue posts 121–137
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
buffer_margin, post #15: post #14 answers the question as asked. The question underneath it is different. Duplicate requests: if several people request the same feature, the requests often get merged. Check whether your feature has already been suggested before posting. Go to post
Requests for platform and documentation features, with the reasoning that justifies them. If you think the site would be better with a feature, suggest it with enough detail that it is actionable.
post #122 is right about the mechanism and I think understates the practical bit.
Deprecation requests: if you think a feature should be removed or changed, that is also a request. Explain why you think it would improve the site.
26 likes 6d
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.
0 likes 5d
Use case: explain why you think the feature would help. "I would use this to..." makes the request concrete.
4 likes 5d
r.coelho, post #3: Coming back to the opening post, because the follow-up matters more than the original answer. Requests for platform and documentation features, with the reasoning that justifies them. If you think the site would be better with a feature, suggest it with enough detail that it is actionable. Go to post
Alternatives: if you have thought of a way the current site might already serve your need, mention it. It helps assess whether the feature is truly missing or just not obvious.
post #126 answers the question as asked. The question underneath it is different.
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.
0 likes 4d
j.baptista, post #14: I read post #12 twice before replying, because I had assumed the opposite. Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised. Go to post
This follows post #126 rather than contradicting it.
Duplicate requests: if several people request the same feature, the requests often get merged. Check whether your feature has already been suggested before posting.
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.
18 likes 3d
Collapsed as off-topic by two members at trust level 3 or above
Requests for platform and documentation features, with the reasoning that justifies them. If you think the site would be better with a feature, suggest it with enough detail that it is actionable.
DSakamoto, post #129: This follows post #126 rather than contradicting it. Duplicate requests: if several people request the same feature, the requests often get merged. Check whether your feature has already been suggested before posting. Go to post
I read post #131 twice before replying, because I had assumed the opposite.
Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.
h.nicolaides, post #100: Effort estimation: some features are trivial to implement; others are substantial work. Staff will estimate effort when assessing whether a feature is feasible. Go to post
Use case: explain why you think the feature would help. "I would use this to..." makes the request concrete.
Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.
30 likes 21h
Coming back to post #135, because the follow-up matters more than the original answer.
Deprecation requests: if you think a feature should be removed or changed, that is also a request. Explain why you think it would improve the site.
3 likes 2h
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Request: show the solution author in the topic list — what changed since
Request: show the solution author in the topic list — what changed since — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation…
|
+85 | 91 | 20k | 3mo |
|
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 |
|
Request: export my own posts
Posting this under the heading it deserves: Request: export my own posts Everything below is what sits behind that. Nominating something for promotion into the documentation commons. The topic in question…
|
2 | 57k | 6mo | |
|
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 | |
|
About the Feature requests category
Requests for platform and documentation features, with the reasoning that justifies them. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is recorded with its…
|
4 | 28k | 9mo |
Related topics — sharing the tags site feedback, translation, wiki post
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
What to include when your question involves a chromatogram — one year on
Asking directly, because I could not find a straight answer: What to include when your question involves a chromatogram — one year on Question in the title. Context below, and I have tried to include the…
|
+69 | 75 | 862 | 14d |
|
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 | |
|
Second pass at: Asking a follow-up: new topic or new reply?
The question in the title: Second pass at: Asking a follow-up: new topic or new reply? I will give what I have already checked below so nobody repeats it. I want to check my reasoning rather than get a…
|
4 | 81 | 8mo | |
|
Request: a diff view for wiki revisions
Request: a diff view for wiki revisions — 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…
|
+26 | 30 | 3.1k | 19mo |
|
Coming back to: What happens when a maintainer goes quiet
Asking directly, because I could not find a straight answer: What happens when a maintainer goes quiet Process question about how this site works. I have read the guidelines and the trust-level page and I…
|
+6 | 10 | 400 | 10mo |