Category:Wiki
We need to agree on the organization of the wiki, category names, and special subcategories.

Don’t hesitate to help out or join the discussion.

Introduction

This wiki has to be clearly organised. If it is not organised logically it cannot be of use. If it is not of use there will not be any vistors. The less visitors there are the less contributions there are to expect. The less contributions expected means that the wiki dies. ;(

Structuring the Wiki

When faced with categorizing a code contribution, the first thing that need considering is whether it’s an application or a single resource (e.g. library, helper, etc.). Generally, a contribution is considered an application if it consists of mulitple files and/or contains one or more controllers.

When this has been decided, you will need to choose a subcategory. It is preferable to select an existing category, as this will make it easier to find related contributions. If none of the current categories are fitting, however, you are welcome to assign it a new category.

This is the general structure that the wiki should adhere to (including a few example subcategories and articles).

Core
.... Tips
.... Intergration
.... Help
Applications
.... Invoicing
........ BambooInvoice
Libraries
.... AJAX
.... Authentication
........ FreakAuth
........ RA Auth
........ Simplelogin
.... Caching
.... Sessions
Helpers
.... Forms
Configs
Models
Views
Controllers

Example

Library

Say we have a new Authorization library we categorize it like Library::Community::Authorization, which will automatically categories it under its parent categories.

Core

Currently

I need to come back on this. I have already started doing many changes and fixing a few typos, formatting some code, categorizing entries as I go along…