Let's hear some concrete suggestions for wiki improvement.
For a start, this sounds like a good idea to me:
At Lowlevel, the quality of the questions was improved a lot after we had abandoned the old "copy this code" style tutorials for individual topics (actually, they are still around, but much less prominent) and guided people towards a new coherent series of good tutorials. "Good" means that they don't just offer code (they do, but usually it's incomplete so that you have to think a bit and can't just c&p), but explain what options you have, where to get information on each of them and how you can integrate the pieces best. In the first part, the provided code is rather complete, and as the series progresses, it becomes less and you have to fill in more by yourself using the links that are given. This way it didn't duplicate the topic-specific articles, but is more like a "guided tour" through the wiki.
Specifically, I like the idea of something that explains all the options, and branches off to "option specific" pages (which converge again as the reader progresses). For example:
Project Goals (e.g. knowing what yours is)
/ | \
Monolithic Micro Exo-kernel
\ | /
/ | \
Assembly GCC CLANG
\ | /
GRUB Roll your own
I also agree with something iansjack said - we probably do need more links to official documentation (if/where possible); and some sort of explanation on how to obtain documentation if a direct link isn't possible (e.g. things like UEFI specs and ARM manuals that require you register and/or sign an "adoptors agreement" before you can download; and places like t13.org
who won't give you official specifications for free but will let you download an "almost as good" draft).