Resources Curation
Took my post from #Void-Chat and pasted it in here.
Okay so I've been mulling over the idea of a #Resources channel. We've gotten a lot of times where it's like -- "Yo there's this really cool guide on XYZ, but what channel can I post it in?" and of course the usual suggestions come up - post it in the relevant #Development or #Topic-Specific channel and it quickly fades. Pin it, nobody looks at pins. #newsfeed maybe, but that, of course, fades as well (or the post simply isn't, you know, news).
So. #Resources. This channel will operate very similar to #projects, in that it is a Fixed-Format channel. Why? Because what the hell good are resources you can't search? Proposed format:
Title: // Something short and catchy
<URL>: // No previews
Description: // Longer-form description going over what a user can expect to find by delving into this resource
Tags: // The basis for searching these things
Now what is partly necessary to augment this channel needs to come from a bot. I'm envisioning a command such as !resources <tags list> (e.g. !resources c# async) that will take a list of tags as a series of AND operators, and output all of the resources found. The output will be a list of titles, with the title linking back to the post itself. Obviously each post in this channel will be logged into a table that relates tags to posts. I'm also imagining the channel as blu+ for write access. Purple+ (or perhaps op+) can review the added resources on mod.gg and potentially remove them.
I'm unsure if this is too much dev work for such a channel, or if we're not envisioning much use of it, but I think it'd be awesome to have an info-dump channel that's easily searchable.
I'm imagining that a server-agnostic implementation would be easy to conceptualize. Any given post can be marked as a #Resource, tagged, and stored in the database. Resources can be searched via !Resource <tags list>.
Can we leave that Description line from that format?
And title could be just longer and contain more information about the resource (if necessary)
The reason I separated it out is because I want a sort of preview of the resources when you search for the tag. For instance..
!resources efcore
Using EF Core in Console Apps --- How Not to use EF Core in a Web API What is Client vs Server-Side Evaluation? --- Optimizing your EF Queries to Improve Performance
Clicking the message will then drag the user to when the resource was posted. The description here can be optional, but I want to give resource-creators the ability to describe their resource a bit more, because the title will have a character limit to conform to discord's formatting.
A good candidate for this would be a curated forum channel, perhaps in conjunction with something like #934 ?