Hello everyone,
I've been thoroughly enjoying my time here on StackInsight Community—the quality of discussion in the API design and microservices threads is genuinely refreshing. However, as I've been navigating the forum, a specific question has come up for me that I couldn't readily find an answer to in the guidelines or pinned posts.
I have a couple of ideas for features that I believe could improve the user experience, especially for those of us who engage in lengthy technical discussions. For instance, I was thinking about the ability to collapse long code blocks within a post for better readability, or perhaps a more structured way to tag "solution accepted" in help threads.
My natural inclination, coming from a background in building systems, is to look for the official "intake channel." Is there a dedicated process for submitting such feature requests for the forum software or community functionality itself? I'm thinking of something analogous to:
* A dedicated, stickied thread in this "Site Feedback & Meta" subforum acting as a running log.
* A formal issue tracker (like a GitHub repo) for transparency and status tracking.
* A periodic "feature request" discussion thread opened by moderators.
I'm asking because a clear, well-defined process benefits everyone. It prevents good ideas from getting lost in general discussion, allows for community upvoting to gauge interest, and gives the moderation and development team a single source of truth to work from. Without it, suggestions can feel like they're being shouted into the void, which is discouraging.
Could a moderator or a long-standing member clarify the current intended workflow? If no formal process exists yet, I'd be happy to help draft a proposed guideline based on patterns I've seen work well in other open-source communities.
—Felix
Totally agree on the need for a clear intake channel. It's something I've looked for myself.
I've been burned before with feature requests just disappearing into a black hole. A sticky thread here feels like the bare minimum. Even better, a public roadmap showing what's under consideration.
Your code block collapse idea is a perfect example. It's the kind of small UX polish that makes a forum feel polished. I'd add inline image resizing to that list.
Demo or it didn't happen
Great question! The lack of a clear intake channel for feedback on the platform itself is a bit ironic, given the community's technical focus.
Your idea for a stickied thread as a running log is, in my opinion, the best starting point. It's low-friction and immediately creates a public record. For transparency's sake, maybe the Community Managers could even post a monthly summary of what they're forwarding to the dev team.
I'd love to see that thread combined with your "solution accepted" tagging idea. It would really help when scrolling through old requests to see what's been acted on, what's declined, and what's still pending.
spreadsheet ninja