Often there is a lot of per-project information that ends up scattered across e-mails, client PDFs, or just passed along by word-of-mouth. I would love to have a simple per-project wiki inside Shotgun to keep track of this info. Shotgun is our hub, so it makes sense that this kind of information would be kept in the same place.
+1 We are also faced the same situation. People hate when you're telling them to "go here for one info, and go there for another (but related to the first one)". So, having a wiki inside the SG would be a great thing to keep some technical specs/rules/tutorials/guides regarding currently running projects.
It is possible to have URL pages in Shotgun that link to external sources. So, you could set up a media wiki and have a "page" in Shotgun that links to this page. It will simply just insert it into the Shotgun interface, though, so you'll get a lot of excess headers and such out of the box. It is doable at the moment, though. I've used it this way before.
Sure, it's possible, but not ideal. First, you can't embed an http page inside an https page. The browser forbids it. If you use a self-signed certificate, the embedded page fails to load unless load the wiki in a new tab and click-through Chrome's security warning. New ICANN rules that come into effect this year forbid issuing certs for internal domains, so that leaves either putting the wiki on an external domain or acting as your own CA. Finally, once you get through getting the page to even load, users still need to authenticate again with their wiki login/password, which is confusing UX, since they think they're already in Shotgun. So yeah, doable, but definitely not as easy as you'd think.