One of the challenges of a mix-and-match approach to open source software is managing updates. Components can sometimes be a different stages in their development cycles when an update is released. Sometimes components are abandoned by developers. That means more testing, longer maintenance windows, and more deliberate reversion planning if there are initial cutover problems. It can also make troubleshooting more challenging if problems are encountered after the initial launch period.
There is much to consider before utilizing non-core software, especially for a support team that is all volunteer.
I'm not saying it should or shouldn't be done. I really like Savio's original idea of having some kind of knowledge base to capture the collective wisdom, even if some if it is completely contradictory!

I had hopes for the wiki approach, but that wasn't secure. Perhaps Simple Content Management is a good option.

I just want people to understand the considerations our terrific volunteer staff must weigh before they commit more of their time for the rest of us who enjoy this community.
--Andy in OKC