Thank you for taking your time looking into this. It's great to hear that you are considering using a CC license, and I totally understand that this is something a company has to reflect on before taking the step.
I just checked the user contributions on the Wiki and luckily the Osiris API section looks pretty clean, so a license switch should be possible for this section. The rest of Wiki, well, it looks more complicated (but I don't know which users are exactly Larian employees). Handling of and working with the Wiki would be a lot of easier if all contents live beneath the same license.
The reason I'm thinking about caching the pages beforehand is that the editor I'm building my extension for offers a feature called "Signature help". It's a little window that pops up every time you start writing a function call. It displays a preview of the function and also can display short help texts. The editor internally triggers the lookup code for that feature on a lot of keystrokes, therefore I need some kind of cache. Also, the short help text sometimes needs to be handpicked from the Wiki, the first sentence of the description is not always a good choice. So currently I scan the Wiki for API articles, create a snippet file with the extracted contents for each API method and review / edit them afterwards. I also use these files to organize all the API calls into categories.
