From WarzoneWiki

This list is made for those people that want to contribute to the wiki, but do not know what tasks can be done. And instead of wasting time by searching articles and thinking about possible ways to enhance their quality a quick look on this list should suffice to give contributers ideas on what they can do. The items are not ordered by importance and anyone may pick any item and work on it.

There may be some more time-consuming items and it would be a horrible waste of time if two persons were working on the same thing. So, if you notice that a specific item is quite time-consuming, please move it to the section Currently in progress and add your nick name and the date in the form YYYY-MM-DD. You may update the date, if you need longer for it. This only works on the basis of trust, so do not misuse it.

If an item on this list is no longer valid, feel free to edit this page.

Currently in progress

To-do items

• Add further browsers to SSL validation errors on Gna
• Update How do I change the screen resolution? in the FAQ
• Add a complete list of the necessary steps for conversion to the section Convert 1.10 mods into 2.1 mods on the Tasks page
• Make License easier skimmable, perhaps by providing important information in a table, schema or list
• Check if the article .wz files is up-to-date and still necessary; if so, add an introduction to it and explain who may use the makedatafiles.sh (to not confuse Windows users)
• Rephrase some parts of Physics engine, unify subheadings, possibly add upsides and downsides of the current state; if the physics engine has changed, add information on the old behaviour and the new one
• Add new other proposals that may be found on the forums
• Check if AI Details are still valid
• Add an introduction to Converting Old Maps, so people know which maps are considered old and why one would have to convert them
• Add an introduction to 3rdPartyPackages, update the article if new 3rdPartyPackages are available
• Add an introduction to Bug Reporting
• Add an introduction to the Compile Guide that tells people what compiling is and if they really need it (add reference to the ready-to-use packages provided by the WRP and 3rd parties)
• Add an introduction to Audit tasks stating what an audit task is and how people can do auditing
• Add an introduction to PIE format that tells the reader what the PIE format is, who made it up initially, why it is/was used and what its shortcomings are; perhaps PIE 2 and PIE 5 should be split into own articles
• Add articles that can be pointed to in the Playing article
• Check if the article on Keyboard Shortcuts is up-to-date
• Add substantial new and unique (as in "not found in other articles") content to Code Documentation or add a new Category "Code Documentation"
• Add information on what a command line option is to the introduction of Command Line Options and give more detailed instructions on how to actually use command line options under different operating systems
• Split the Campaign walkthrough into smaller pieces, at least one article per campaign to ease the use of the document