This page is mainly dedicated to describing best practices for using a wiki to manage copy, that is, the editorial content, for a paper-and-ink publication, but most of the ideas are applicable to web publishing too.
Because the title (or even the author) may change or may not be immediately obvious, use an arbitrary page name for the article text. DanielMacKay uses the day the article was originally submitted or proposed plus an arbitrary serial number, e.g. for the third article on November 25th, 2005, the page name is 061125-03. "I have a separate mySQL database to keep track of the metadata - author, title, word count, expected/have/proofread status, and which issue the item will be used in," says MacKay, "contact me for details if you're interested."
Write a plain-english guide for editing articles in the system (as a page, of course.) Don't mention the word "wiki" or you will frighten people. Just tell them they can click on "Edit This Page" at the bottom, make changes, and later click "Save" and that everything is saved, and that even if they accidentaly erase something, it's very easy to retrieve.
If someone submits material before deadline, mail them back with the URL of their article, and the URL of the guide and tell them they can tweak their article up until deadline.
Remind your writers and proof-readers that it is impossible to permanently mess up the text, and that there are several overlapping backup systems protecting the articles.
Actually have, and regularly test, your backup system as well as the RecentChanges system.
Use a wordcount module (in Oddmuse, "wordcount.pl") to help writers and editors meet their word count targets. It's a little piece of JS which shows how many words are in the edit window at the moment.