I would suggest a new simple policy for the site, related to answers. Every answer should:
- Refer to some officially recognized body of knowledge (PMBOK, Agile Manifesto, PRINCE2, RUP, MSF, Scrum, Kanban, etc)
- Generalize the question
- Point readers to new subjects of learning
For example, somebody asks "How detailed technical documentation should be in a small project?"
A possible answer may sound like: "I would recommend to document technical decisions in high-level UML diagrams, and revise them every sprint/iteration. In general, Agile Manifesto recommends to focus on working software instead of documentation, although I recommend to read CMMI TS process area which explains the importance of technical documentation. Read Martin Fowler's "UML Distilled" and Len Brass et al.'s "Software Architecture in Practice"".
This answer (just an example) contains author's personal opinion, grounded by two standards. It also generalizes the question and gives the reader some direction of further learning.
By "generalization of a question" we should mean an ability of the answering person to present the problem from a higher point of abstraction than it was originally asked. As in the example above, somebody asked about documentation in a small project, while the answer also talks about documentation in general. Generalization is an opposite to specialization, which we should try to avoid in our answers.