From the PoV of someone who has managed a home-grown wiki and written a home-grown wiki, if you guys do do this, can you not make the wiki home-grown? There's a million and one wiki packages out there, most of them are awesome, and it's a hell of a lot easier to make the user db shared (Does hubski use a sql / ldap backend for users?) and skin it similarly than it is to write a whole new wiki in arc and integrate it with the normal site. ikiwiki is great, moinmoin is great, I'm neutral about mediawiki, but there's wikis written from scratch for a specific website almost always lack polish in every aspect and are damn hard to get right. Even if it doesn't share the dark / light skins, even if it has separate notification preferences... as long as it shares the same user and password, whatever you guys roll with would be solid in my book. 2c
We are definitely not going to brew one up. I'm not sure if the one that joelg236 created will suffice. I'm open to hosting a package. That way there are no adverts, and it's under our control. I am sure there are basically one step deployments for Digital Ocean droplets. I'll talk to forwardslash about the realities of account integration between the two.