I propose that Stack Exchange evolve to support more of a crowd sourced documentation model than just questions and answers. Please don't dismiss this as heresy. The great thing about Stack Exchange is that it encourages the community to create clear, concise, accurate answers to questions or problems that people have (eliminating the snide, cryptic, rambling discussions of the old listserv and forum systems.)
I think most people go to Stack Exchange sites to get answers (to questions other people have already asked). The clear answer is (usually) more important than the question. What would happen if we took the answers and organized them in some sort of taxonomy (or more precisely a directed (not necessarily acyclic) graph) of related answers / gems of information? Stack Exchanges would become responsive, crowd sourced, organized documentation.
The questions and (multiple) answers and comments would still be a major engine of generating information -- as well as getting answers for the people who first ask the questions. I guess the 'documentation' 'view' of Stack Overflow would be a alternate rendering of the database of answers (and questions and comments). It doesn't have to replace the Q and A rendering of the information.
One major advantage of the 'directed graph' (that is, outline organization) of the information is that people can find closely related 'answers' to what they are looking at. I've recently been trying to compile dynamically linked C programs for Android/Linux and found lots of goodies on Stack Overflow. However, if when I found one answer related to Linux -> Android -> linking/loading -> dynamicLoading -> /system/bin/linker, I may see other related answers/documentation about dynamicLoading or how to use LD to create a .so file. Web searches for information (on Stack Overflow) is great, but finding related information by proximity is another valuable way to find things. (This organization is not free, but it is worthwhile).
Second, we might encourage people to write answers (even more) like a tutorial or documentation. People have been doing that already -- not just answering the specific question, but explaining the issue in a general, more broad way than exactly what was asked in the question. Further, we could tolerate (or encourage) people to just post answers (documentation) rather than putting the information out in the form of a question -- with accompanying answer. I think I now understand my (not yet posted) question about how dynamic linking works in Android/Linux/C. I can see that other people have been having this problem. I'd like to be able to just write a few paragraphs with what I've learned. -- Stack Overflow shouldn't reject this valuable knowledge just because it isn't a question posted by one person and answered by another.
I'd like to see Stack Exchange evolve into more of a question-driven WikiPedia. What do you think?