...

Mostly.  Same comment here (again). 

 JJKP

Some general thoughts that I think need to be addressed at some point, though I don't have a solution right now:

• Some info should be categorized in multiple places. For example, users care about how to submit bugs, but only contributors (participants) need guidelines on reassigning and triaging them. Developers need compile instructions, but users do, too (since they may be downloading a source bundle). Core API docs are for developers only, but C API docs are for users. We'll just need to flesh out these relationships as the wiki matures.
• We need one wiki "owner" that makes sure things are moving smoothly. Sub-pages should have separate curators, but I vote for having one POC for the entire thing, to herd everyone in the right direction.

And some specific items:

• We spent some time brainstorming wiki topics; these should be included in the list.
• "Participants" seems too small for a top-level heading. I prefer something like "For Users > About Us" that links out to pages that describe the team, participants and contributors, links to other websites, etc.
• Agree that we need to figure out how to make the left-side menu more consistent and useful.
• Agree that "Governance" as a heading could be improved. Maybe "Project Management" or "How to Participate" or "GMAT Project" - none of these seem good, but you get the idea.