Utility: Official release of the unofficial Dominions 3 Wiki

[JonBrave]

Originally Posted by lch

You know, that would be exactly what I'd have asked if I was in your situation. There should be a "live" version and a "testing" or "development" version of a website, and changes should only be pushed from the "dev" to the "live" version when they're finished. When I was working on web design things, I always kept things that way. With the Wiki, I haven't done such a setup, mostly because it was overkill and because I am usually not working on the live code, but just install and upgrade code from the official SVN codebase now. When I started on the Wiki, I didn't need such a setup because nobody knew about it and I was free to do whatever I wanted to do without the need to have a working "live" version while I'm developing. Now that there is some customer/user base who needs to access the Wiki even when I'd need to work on it, I would favor and use such a setup, yes. In case I ever intend (and have time) to work more on it, I think I'll work on a cloned version like you have considered, yes.

Dear Mr Ich,

I think some people didn't like how I asked! I'm glad to see you take it the way it was intended

Here's what I don't get/is sad. Your Wiki is, or should be, 99.9% static text. No offence intended, but as I recall it's just clicking on links to other pages (little if any interaction) --- which is fine, and as it should be. A few years ago, as I recall, the site would have been some pages & links, and that could be plonked anywhere. Nowadays, it seems, you all need "engines" & "scripts" to deliver your sites. Hence all the issues about your site being "down". That's the bit I don't get? Let (suitable) pages be just static content, or if necessary generate it at some point and save/offer that?