| 29 | |
| 30 | == Documenters == |
| 31 | |
| 32 | There are two main parts of documentation - user and developer. User documentation helps people get started with the tool or use advanced features, while developer documentation helps people understand the API so that they can get to grips with it or write plugins. |
| 33 | |
| 34 | Once we approach our first stable release then contributions of user guides could be put together in the [http://forums.hiveworldterra.co.uk/viewforum.php?f=39 forums] before being copied to the main website. |
| 35 | |
| 36 | Most of the developer documentation should be written as the developer's write the API (documenting what public methods do so that they can be tested and so that they have a defined contract of what they will do given certain inputs). A large enough project is always difficult to get started with though, so introductory tutorials adding small features or step-by-step guides to creating plugins may prove useful. |
| 37 | |
| 38 | == Designers/GUI/Graphics == |
| 39 | |
| 40 | A lot of open source applications can be functionally great but have a poor user interface and it can be a poor user interface over a great program that puts people off using it. The split between a back-end API library and front-end UIs makes creating new interfaces easier, but input on existing interfaces, new icons and other graphical feedback would also be appreciated. Any contributions should generally be posted in the [http://forums.hiveworldterra.co.uk/viewforum.php?f=39 forums], but designers/graphics contributors may get developer accounts on Trac and Subversion if useful and necessary. |