You bet, and thanks for clarifying the category topics. There’s a nice second benefit to these categories as set up: you can think of them as a spectrum or a cycle.
So let’s pretend elm-benchmark doesn’t exist. I start off in Learn: “how are people doing performance testing?”. Cool, I learn some stuff, like harnesses around benchmark.js.
Then, I’m like “we should have a benchmarking library… but I’m not sure what it should look like.” Those ideas go in Request Feedback, and the community collaborates.
Then, finally, I write something (handwaving over the native code in the actual package for the moment.) Once it’s done, I show back up in Show and Tell with the announcement.
Afterwards, I need to add more features. Back to Learn, then Request Feedback, and maybe Show and Tell when/if they get added.
My conclusion: if people use these categories in this way, it sets up virtuous cycles where nice things get made collaboratively. Does this seem like a reasonable way to moderate this forum?