Very nice piece of prose again @sfws but this is not going to be very useful or helpful. Repetitive crying for help apparently does not help.
What is required is somebody responsible for the structure so that some may take subsets in control and other people, development and users, may add info. And it is very clear you do not want it so it is not going to be you. To be honest, the best way is simply to take your hands off completely, let the wiki drift and wait until somebody picks up.
Managing the wiki does NOT imply writing everything and writing does not imply managing everything or taking responsibility for the total. You say yourself:
It needs to be done by someone (or a group of people) who understands all.the functionality of MX
So start with somebody responsible for global structure and final redaction. Then assemble writers, make divisions in user interface, technique, inner working, parameters etc... Make empty shells to fill in and the invite writers. Create a hierarchical structure with cross connections (in visual schema is necessary for others to see what the structure is).
I did not ask to be asked for being responsible for the total overhaul of the wiki, I merely asked for restructuring of the subset of pages dealing with FTP. I have other things on my mind than being responsible for the wiki and you know that. So don't start this on my question, it does not serve a purpose and does not answer my question. Neither is this crying act inspirational for others afaics.
I offer to add info, not to take responsibility so don't reply in that sense, it does not help.
And make a note on the opening page about participating in the wiki more prominent and less 'oh if you intend to write ...'. Nobody will write unless you invite
. Make the opening note something like: this wiki exists only by contribution from its users so : CONTRIBUTE! Contact : 'the manager' and ask what you can do. Once in a while somebody may contact that manager and then be prepared and have sections ready which need to be filled in. Prepare, organise and summarize.... then after writing: check, review, control. And if still within the lifecycle of the page: modify. Pages at the end of their lifecycle: archive and rewrite when the subject is still necessary. Limit the pages in content: users don't need history (that's a separate page), users need operational info.
A community is more than individuals making things and then leave it because individuals have their limits as you yourself have made clear.
Believe me Linux is not just Linus T. Cumulus is more than Mark C.
It is, or should be, organisation. So organise.
Edit: start by organising/asking those ghost contributors with write access: non-existent: delete. Existent: ask.