Use proper formatting on the Wiki pages, especially the development documentation.

   This is code..
      Properly indented 
   and formatted

This is a Level 0 heading

This is a Level 0 heading

• this is a bullet list
  • with nested elements

1. this is a numbered list
   1. with nested elements
   2. in sequence
2. ...

etc.

This allows for using other facilities of Trac that rely on such formatting, such as Table of Contents, PDF export, etc.

Attach and include screenshots where applicable (attachment permissions have been fixed). Attach other documents where applicable as well (although they should preferably be added to SVN and then linked accordingly which makes management bearable).

The easiest approach is to export the tooling as a plugin. Investigate how this can be best achieved and possibly automated (e.g. for nightly builds).

Alternatively, a lightweight and environment independent solution would be to deploy the tooling as an RCP application. Investigate how this can be best achieved and what possible drawback it may entail. If the effort is too high, this option could be postponed or discarded.

Partially implemented features may be closed as well with a note on the state of the implementation and open issues. If there is a need for further work on these tasks, they will be reopened in the future.

Relevant commits may be indicated by appropriate trac-links.