Sorry, will never use Wikia or a "multi-host-site" environment similar to that.
- have server, or host, depending
- select a base engine (Wiki, Drupal, Piwigo, Wordpress....etc) for the site
- build the site framework and mod the engine as needed
- document all code changes
- make some kind of content related graphical solution, usually as a sub project with help
- add content
- keep on the look out for security patches to the engine
- no ads, never
- etc stuff that you can do when you are 100% in control. Not 99, 100.
If you consider my approach more work and less "out-of-the-box" than Wikia, you are right, but the site can be moved around, it has no ads, it will be properly backed up, the solutions and layout selections are endless (only limited by the "engine"), you have direct access to files for changes, you have direct access to database for that (if needed) and I can secure it way past the options of those other solutions.
I would love to keep working on my sites, but I need a team. Like the Wiki I have tried to work in, but I will not just copy-paste what other sites have, and thus I am limited to figure out my own stuff which is a challenge when so much has been posted in so many places.
Also I have taken to use Project Engines to a certain extent that I have available, where one can track and follow and discuss everything related. Sure a forum will do nicely, but it seems over the top to implement a forum on a site that will not have use for it, so I keep it separate.
(and these days it feels nice to have zero hosting in US or NATO countries... for what it's worth)