Introduction for developers to Posterno

Posterno has been coded with developers in mind, the code is well laid out, easy to read, and documented. The source code for Posterno is also highly extensible, which makes it easy for developers to hook in custom functionalities, or modify existing parts of the plugin.

Github - For Tracking

The entire source code of Posterno is available on Github. This is also the place where bugs and enhancements are tracked. Furthermore milestones are created as an easy way to track features and fixes that are released with each new update.

Code Organization

The source of code of Posterno is organized in separate, meaningfully named files and folders.

Functions and Classes naming

All functions, with no exception, are prefixed with "pno_". This helps ensure that the plugin does not cause any conflict with other plugins or functions with similar/same names.

For example, do not create functions named like this:

function my_function() { 	// Your code here } 

Instead, you should do this:

function pno_my_function() { // Your code here } 

PHP Classes should also follow the same naming rules.