If you would have to standardize wikis for software development projects, how would you structure them?
Such a wiki template, I think could contain items such as...
What other items in your experience would be critical to be included in a project wiki?
Isn't the whole point of Wikis that they can evolve over time to fit the nature of the project. I wouldn't enforce too rigid a structure on them or you'll end up stifling their benefits.
If you do want a structure, I would say "coding guidelines" should be company wide, not specific to each project, so I would move that up a level. Also, how about areas for requirements, specifications, user manuals, common problems [and their solutions].