<p>I'm thinking of starting a wiki, probably on a low cost LAMP hosting account. I'd like the option of exporting my content later in case I want to run it on <code>IIS/ASP.NET</code> down the line. I know in the weblog world, there's an open standard called BlogML which will let you export your blog content to an <strong>XML</strong> based format on one site and import it into another. Is there something similar with wikis?</p>

[{'answer_id': 38835, 'author': 'Till', 'author_id': 2859, 'author_profile': 'https://Stackoverflow.com/users/2859', 'pm_score': 0, 'selected': False, 'text': '<p>I haven\'t heard of WikiML.</p>\n\n<p>I think your biggest obstacle is gonna be converting one wiki markup to another. For example, some wikis use markdown (which is what Stack Overflow uses), others use another markup syntax (e.g. BBCode, ...), etc.. The bottom line is - assuming the contents are databased it\'s not impossible to export and parse it to make it "fit" in another system. It might just be a pain in the ass.</p>\n\n<p>And if the contents are not databased, it\'s gonna be a royal pain in the ass. :D</p>\n\n<p>Another solution would be to stay with the same system. I am not sure what the reason is for changing the technology later on. It\'s not like a growing project requires IIS/ASP.NET all of the sudden. (It might just be the other way around.) But for example, if you could stick with PHP for a while, you could also run that on IIS.</p>\n'}, {'answer_id': 38851, 'author': 'Scott Bennett-McLeish', 'author_id': 1915, 'author_profile': 'https://Stackoverflow.com/users/1915', 'pm_score': 4, 'selected': True, 'text': '<p>The correct answer is  ... "it depends".</p>\n\n<p>It depends on which wiki you\'re using or planning to use. I\'ve used various over the years <a href="http://moinmo.in/" rel="noreferrer">MoinMoin</a> was ok, used files rather than database, <a href="https://help.ubuntu.com/" rel="noreferrer">Ubuntu</a> seem to like it. <a href="http://www.mediawiki.org/wiki/MediaWiki" rel="noreferrer">MediaWiki</a>, everyone knows about and <a href="http://jamwiki.org" rel="noreferrer">JAMWiki</a> is a java clone(ish) of MediaWiki with the aim to be markup compatible with MediaWiki, both use databases and you can generally connect whichever database you want, JAMWiki is pre-configured to use an internal HSQLDB instance.</p>\n\n<p>I recently converted about 80 pages from a MoinMoin wiki into JAMWiki pages and this was probably 90% handled by a tiny perl script I found somewhere (I\'ll provide a link if I can find it again). The other 10% was unfortunately a by-hand experience (they were of the utmost importance with them being recipies for the missus) ;-)</p>\n\n<p>I also recently setup a Mediawiki instance for work and that took all of about 8 minutes to do. So that\'d be my choice.</p>\n'}, {'answer_id': 38873, 'author': 'Guy', 'author_id': 1463, 'author_profile': 'https://Stackoverflow.com/users/1463', 'pm_score': 1, 'selected': False, 'text': "<p>To answer your question I don't believe that there's such a standard as WikiML as Till called it.</p>\n\n<p>As strange as it sounds, I've investigated screen scraping a wiki for a co-worker to help him port it to another wiki engine. It turned out that screen scraping would have been easier, quicker and more efficient to write to move this particular file based wiki to another one or a CMS.</p>\n\n<p>Given the context that you wrote the question in I would bite the bullet now and pay the little extra for a windows hosted account and put Screwturn wiki on it. You're got the option of using file based or SQL Server based back end for it but because one of your requirements is low cost I'm guessing that you would use file based now for a cheaper hosted account and then you can always upscale the back end to SQL Server.</p>\n"}]
['https://Stackoverflow.com/questions/38824', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/5/']