A concern was voiced about a recent question we got about all of the abilities in League of Legends. You could similar questions to this for games like Sora or Star Ocean 3 or numerous other games, without issue. That's because they're static - you'll never need to update them once you've compiled everything, barring the presence of the exceptionally rare patch/update.
It's very different for games like League of Legends, or Team Fortress 2, which are not only updating but frequently updated. This is far from the first we run into these - this answer dates shortly after our private beta ended, and even without playing TF2 I can tell you that the list is beyond outdated. And thus we have our problem - dynamic games like these require very high maintenance for questions like this.
One of the problems I voiced long ago with regards to repositories is that of "Motivation for Quality". Our mission in being an awesome resource that has the answer people are looking for, this demands us to try and stay on top of things. This is why we have continuing discussions on what to do about all our old content about how things worked in older patches. These questions, however, don't simply change on a patch here or there - they're fully expected to be different with each iteration, they're demanding maintenance. Unfortunately, maintenance of our own guides is a bit problematic because as time grows, our own content will grow. Not only will the job of maintenance become practically full-time, but it will also start to cloud new content.
How can we address the issue of high maintenance questions like these? How do we prevent them from being either an out-of-control beast, or an un-updated sack of lump that has long lost its sheen of usefulness? What strategies do we have that can handle these without interfering with the normal flow of activity on the site? Or should we consider that we must change the flow of our site to accomodate these?