To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

Large parts are about improving an existing aircraft. This should be split off to a separate article.

Large parts are written like as if the authors was not aware of the more specific articles existing that covers a most of the subjects mentioned. I feel that the article should only go into the very basics and provide pointer for the rest. There is much enough ambiguity on this wiki as is.

I strongly believe the article structure of the wiki should have very little overlapping except what is needed for context, in essence DRY (Don't Repeat Yourself)

It would also be wonderful if new editors could somehow be educated to understand that categories are not tags. Presumably they expect images to be easier to find if they add as many categories as possible (that still seem at least remotely related).

I would consider that better file names and file descriptions (as well as some linking) probably is more efficient.

Documenting undocumented templates

FlightGear wiki namespace

Policies

There is unfortunately a growing need for policies. Like with categories I strongly believe that they should form a tree, with a general unspecific, very concise and more or less universally agreed on policy at the root.

As these will be used both as guidelines for users, as guidelines for users wanting help from administrators and as guidelines for administrators, there will need to be some form of consensus about them as well as a policy describing how to propose new policies, changes in existing policies and amendments to polices.