The aim of the API Reference Project is to construct a useful reference manual on the Joomla 1.5 (and later) Framework API which will complement, rather than replace, the automatically generated material on http://api.joomla.org. The starting point for the API Reference is the Framework page which lists all of the classes in the Framework API.
If you would like to help us with this massive project, then all you need to do is register on this wiki. You don't need to join a Working Group and you don't need to ask permission. You just register and get started. A good idea is to pick a class you know something about, or have spent time researching, and start there. Also feel free to add examples, improve explanations, or correct mistakes on existing pages.
We are only documenting the classes in the /libraries/joomla directory. These are the Joomla Framework classes. Some of the material developed on the wiki API Reference will gradually be merged into the phpDocumentor tags in the source code itself and hence will end up on http://api.joomla.org too.
Our inspiration is the online reference manual for PHP. For example, see this page: http://www.php.net/manual/en/function.echo.php which can be accessed by a simple, clearly defined, standardised URL and which permits user comments to be added.
The starting page for the API Reference is the Framework page (Joomla 1.6 Framework | Joomla 1.5 Framework where you can see a complete list of all the classes in the API. Each class will be given its own wiki page linked to from the Framework page. Each class page includes a list of all the public methods available and each of those methods will also have its own page (actually a "sub-page").
To simplify the documentation process, the class and method pages have already been created automatically. We reduced the documentation process to three pieces of knowledge, only humans can provide:
Sources of information that might be useful when writing for the API Reference:
Each class and method need a comprehensive description, so novices understand the idea behind that class/method. Explain what it's used for. If you wish you can add information to the design pattern that this class represents, and the concept behind it. Find a balance between useful information and technical detail. Don't be too generic, but do not start to explain HOW the class/method actually does the work. If the user wants to know about that, he/she will look at the source body provided within the method page.
In order to edit the description, click on the "Edit description" link on the top right of the page.
The See Also section collects valuable links the provide further reading to that class or method. Provide links to wiki tutorials or other resources of use that might help the user to fully understand the functionality of this class or method.
One very important resource for help novices understand and learn about the Framework are code examples and comments of experienced users. Show the user how the class/method is used. Start with an easy example, then go on and maybe solve a fictive problem with the help of that class/method. If you've just learned about the way a certain class or method works, this is the perfect time to spend 10 minutes of your time, and write down what you've just learned. It will save hundreds of fellow developers hours of their time and your work will be highly appreciated.
Adding a code example is very easy. Once you're logged into the wiki, you'll see a "Leave a comment..." link below the "Examples" heading of the class/method page. Click on it, and a form will pop up, where you can enter your comment or code example.
You can use every wiki markup, within your code examples.
If you want to include PHP code in your example, frame the code with <source lang="php"> </source> tags, so the code will be properly highlighted.