<p>(Preliminary question: Is our FAQ editable at this point? If so:)</p>
<p>I have recently started being more active in reviewing.  Mostly, of course, you review a new user's first questions, and are often called upon to comment to help familiarize the user with the site's operation and features.  It is common to point the user to our <a href="https://stats.stackexchange.com/faq">FAQ</a> for info on asking questions (I'm also quite enamored of this blog post by @PeterFlom: <a href="https://web.archive.org/web/20160407121308/http://www.statisticalanalysisconsulting.com/how-to-ask-a-statistics-question/comment-page-1/" rel="nofollow noreferrer">How to ask a statistics question</a>, which does a good job of covering material not included in the FAQ).</p>
<p>Sometimes, however, I review a new user's <em>first answer</em>, and feel obliged to comment in an  analogous manner.  Unfortunately, there seems to be less available to point people to.  You can still recommend reading the FAQ (it certainly doesn't hurt), but that information is more geared towards question askers, rather than answerers.  Sometimes I think the <a href="https://stats.stackexchange.com/about">about page</a> might be helpful, if only because the figure can spark the idea that we don't simply want to help answer the OP's question, but that an ideal answer spans all four types of content / goals.  Nonetheless, that page is pretty sparse, and not oriented towards informing new answerers about what makes for a good answer, etc.  I am aware that there are some meta threads (both <a href="https://stats.meta.stackexchange.com/questions/1218/how-should-performance-answering-questions-best-be-evaluated/1248#1248">here</a>, and on <a href="https://meta.stackexchange.com/questions/136294/what-makes-an-outstanding-answer">SO</a>), and perhaps some SE blog posts, that are pertinent to answering questions well, but the mere fact that there are several means that that information is not centralized.  In addition, they are not very accessible to someone who wants to throw out a quick (but hopefully helpful) comment.</p>
<p><strong>Should we include such information in our FAQ?  Can we?  What should that / those sections contain?</strong></p>
<p><em>Note that the following meta thread exists: <a href="https://stats.meta.stackexchange.com/questions/6/what-should-our-faq-contain">What should our FAQ contain?</a>, but I thought it better to ask a new and focused question, rather than add this idea to the list of old answers there.</em></p>
