<p>I was recently put in charge of the wiki for the development team. The wiki is still in its infancy, so I have a lot of room to work with. It goal is to house internal to the development team. Currently, the main piece of information that the wiki holds is Coding Standards. </p>

<ul>
<li>What are some best practices your dev team uses for its internal wiki?</li>
<li>What information is important to have on a dev wiki? </li>
<li>If you were to go to the wiki for your dev team what information would you expect to see? </li>
<li>Is there some information that shouldn't go on the wiki even though it seems like a good idea?</li>
</ul>

<p>-- edit --</p>

<ul>
<li>Also, is there a good way to organize the information? ( such as by layer ( data, ui), by porject, or other) </li>
</ul>

Introduction to the source base for new programmers
General documentation (not the API documentation per-se, but more tutorial like things)
Lists of staff / who's doing what and how to reach them
Notes / resources / articles that explain concepts used in the software
Documentation of the build process and the filesystem layout of the codebase
Other things I usually put up there are
Planning / todo lists
Information that is interesting for others to read
Everything else that I feel should be shared