Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Editing tag descriptions is a privilege, currently based on reputation. (Changes to the privilege system are coming, but not yet.) The threshold is currently set at 250 rep. I recognize the boot...
Answer
#1: Initial revision
Editing tag descriptions is a privilege, currently based on reputation. (Changes to the privilege system are coming, but not yet.) The threshold is currently set at 250 rep. I recognize the bootstrapping problem of a new site, particularly one that doesn't have moderators yet. Please feel free to add proposed descriptions in answers here and I (or someone else with admin privs) will drop them in for you. I'm hoping that as activity picks up, it won't be too long before community members can do this directly. We could lower the limit further if that's what folks here prefer; please let us know. As far as guidance is concerned, the *first* job of a tag description is to provide enough information for someone who's about to use it to know this is the right tag. Sometimes that'll be obvious from the tag name, but if it's not, please convey *usage intent*. The longer description can flesh this out more and link related tags. On SE, there was the occasional tag wiki that was more of a canonical post or thorough article about the subject. That information is great to have, and SE didn't provide any other place for it. It was also the case that people didn't always find that excellent information when looking for it; tag wikis aren't an intuitive place to look for many people. The community here is welcome to build out those kinds of tag wikis if y'all think that's the best approach, *but* consider other options too. This community can have categories beyond Q&A and Meta. Cooking has [Recipes](https://cooking.codidact.com/categories/29), several sites have challenges ([example](https://writing.codidact.com/categories/20)), Electrical Engineering has a forthcoming [Papers](https://electrical.codidact.com/categories/35) category, and Meta has a [blog](https://meta.codidact.com/categories/30). Notice that some of those categories have *articles* rather than Q&A. If the Software Development community wants a blog or a reference category or something like that, we can set it up and you can post information there that will probably be more visible than the tag descriptions.