AS A ???
I WANT ???
SO THAT ???

djce writes: Before we change any systems, let's work out what we're proposing to change and why. Hence, TODO fill in user stories below (in the description field, not the comments). I'm only too happy to explain what I mean and why, if it's unclear. Once the user stories are complete, step 2 will be acceptance criteria, and step 3 will be tests. Implementation lies somewhere beyond step 3.

AS AN editor of the wiki
I WANT the wiki API to work
SO THAT I can use the API to automate maintenance of pages with scripts (e.g. double redirect fixers, automatically updating generate-able lists, etc.)
AND SO THAT I can use the API to create backups of the wiki external to MB

AS AN editor and reader of the wiki
I WANT SpecialPages to be structured (e.g. as provided by MediaWiki >= 1.13.0)
SO THAT it is easier to find the pages that I want

AS A sysadmin
I WANT an off-the-shelf wiki as possible (ideally, installed from vendor packages)
SO THAT I feel confident in the wiki's stability and security
AND SO THAT future maintenance is reduced

AS A wiki maintainer
I WANT to be able to customise the site styling without involving the sysadmins
SO THAT I can make changes quickly

AS A wiki maintainer
I WANT the wiki styling to use a mediawiki-supported mechanism
SO THAT the system has a lower long-term maintenance cost
AND SO THAT mediawiki documentation accurately reflects the MB wiki

AS A wiki maintainer
I WANT the existing wiki content (pages) to be kept across any rebuild or upgrade
SO THAT we don't have to type everything in again

AS A wiki maintainer
I WANT the existing wiki users and groups to be kept across any rebuild or upgrade
SO THAT we don't have to type everything in again

AS A musicbrainz-server hacker
I WANT ??? (TODO: upon what wiki features does wikidocs depend?)
SO THAT the wikidocs feature continues to work
Since the requirements here involve both URL access and the HTML structure of rendered pages, I suspect that this requirement is going to be addressed by testing musicbrainz-server against an upgraded wiki before going live, in order to find out what - if any - changes need to made to the wikidocs code.

AS A sysadmin
I WANT the wiki to be accessed via the gateway nginx
SO THAT we have simple http log stats (nginx-rrd)

AS A sysadmin
I WANT the wiki to use one of mediawiki's preferred (supported) URL structures
SO THAT the system is more supportable

AS A wiki editor or user
I WANT URLs of pages in the current wiki to continue to resolve to the same wiki pages (as far as possible)
SO THAT (if we change URL structure) the old URLs don't break

AS AN editor and reader of the wiki
I WANT our customizations to the interwiki table (e.g. recording/artist/editor/etc. prefixes) to be re-created or copied upon upgrade
SO THAT pages in the wiki that use these types of links continue working