Miraheze migrated to a new server host yesterday and had to disable all file uploads while they did so, so it may be related to that. And actually yeah, their discord has an announcement that says:
"We are aware of issues where some wikis are unable to upload files, or are experiencing issues in thumbnail rendering. We are trying to resolve this as fast as we can, but we don't currently have an estimated time as to when this will be resolved. We apologise for the inconvenience this may cause, and thank you all for your patience"
Discord is here: https://miraheze.org/discord
I also use Namecheap's hosting and you can install mediawiki (or DokuWiki, if you want to try it) with Softaculous, which is probably what you used to get wordpress. In the softaculous section of cpanel, click "wikis" and you can choose from several wiki software options, the install instructions should be fairly straightforward from there. You could also try making a subdomain (wiki.website.com etc) to test on before completely getting rid of your existing wordpress site.
Netlify is more like the host itself, like the cpanel of your namecheap hosting except specifically dedicated to working with site generators like Jekyll, so you can't really use that particular part of it unless you want to change hosts. Honestly if you want to try out Jekyll, your best bet is probably testing on Github Pages since it's free and built in (so you don't really have to do any complicated installation other than just leaning how to work github). If you like it then just skip namecheap's hosting altogether and just use your custom domain name to point to github. It is possible to install Jekyll on namecheap hosting but from what I can tell it's a pretty huge hassle unless you have a dedicated server plan (which the "Stellar" plans are not).
Web building is absolutely a complicated mess and at some point the easiest choice may just be the best choice even if it's not the most "suitable", so at the end of the day you may just want to go with a wiki software anyway if that solves the problem with the least pain.
mediawiki is right for you if the type of content you (and your users) want to add is similar to the biggest mediawiki of them all :-)
as people mentioned already installation and customizaton should not be that hard. what you should probably focus on is how you will port / create the content.
take a look also at static site generators
github pages is a hosting solution, and you can use a static site generator with it, e.g. here's Hugo's docs
Coding isn't necessary, but it does help mostly because you tend to be used to a lot of random confusing setups and command-line interface (CLI) stuff once you've been coding for a while.
I would definitely recommend against self-hosting WordPress, but if you can find a place that will host for you, that will probably work for what you need.
> In this case I would not want others to contribute to the wiki at the moment as that's not the purpose of this website.
If you NEVER want anyone else to contribute to the site, maybe a static site generator like hugo is a better bet? (that's what I use for my personal blog, but it's not restricted to blogs) MediaWiki is pretty complicated to sysadmin, the primary benefit of it is allowing others to contribute.
No problem. When you revisit it, here's the link to removing PHP. Just backup the config file first so you don't hose IIS.
Reinstall through Microsoft PI assuming IIS of course. It should pull down the PHP plug in too.
If you install PHP and MySQL accepting the defaults you should be fine when connecting/configing mediawiki. I did this on W7 for proof of concept. The real fun will come getting it to work on Server 2012. Just waiting on a coworker to get the VM on line.
Its quite easy to set up a stock installation. It can get more complicated if you want to play around with customization, but most common stuff is already possible with extensions. If you want something even easier to set up yourself, an alternative could be dokuwiki which does not require a database.
Is this on Mediawiki.org? If so, you have to place:
{{collapse top}}
before the text you want to hide/collapse then place:
{{collapse bottom}}
after the text you want to hide/collapse.
If not, you're going to have to create a template that collapses text. It won't be as easy as copy pasting everything in the source code because that source code is filled with other templates and parser functions. So if your wiki doesn't have them, you won't be able to use that template until your wiki has everything that calls for that template to work. Adding parser functions to your wiki would require installing certain extensions and that's a more advanced than my skill level. You would have to talk to the people running your wiki about that.