Common Requirements:

1. Code convention
   All files should be written according to the Code Convention.


2. Demo
   Each product should be represented by screenshots, or a demo site, or any other way you can (screenshots, slideshow, portfolio, demo site).


3. ReadMe File
   Complete and structural ReadMe file (file name, build, version compatibility, installation etc.).


4. Installer wizard
   Installation should be presented as a php installer file to make it easier. Process the SQL queries without any accesses to the phpMyadmin, language keys, menu blocks, menu items adding etc. - everything should be done automatically by processing this php installer.


5. File naming
   The software should contain the product name and version in its name(the build number, if necessary).


6. Version compatibility
   A product marked as compatible with Dolphin 6.1, for example, should be fully compatible with the mentioned Dolphin version without any additional necessary software or procedures.


7. More than 1 file
   Each product should have more than one file, and the package itself should be packaged properly:Folders and files, not all files in one folder. For example, classes folder should contain php files, js folder should contain all JavaScripts files, layout folder should contain design files, (layout can consist of several folders such as css, images, html, data etc.). Uploading a product consisting of only a readme file is strongly prohibited.


8. Legal distribution
   To be able to offer products (integration modules, Copy and Paste Scripts, etc. ) which have proprietary or other private licenses, you should have the right to distribute it. You will have to grant your resellers rights.

Extensions:

1. Admin panel
   Each product offered here should have admin panel with enable/disable options as a minimum, so the site administrator will be able to turn this module on/off at any time.


2. Additional functionality
   Any product offered here should provide additional functionality, Not bug fixes.


3. Do not over-write Dolphin, Orca files
   You shouldn't over-write Dolphin files and then compose your installation manuals with something like: "take this file from my package and upload it to the Dolphin directory..." etc. Your over-written files could destroy another part of the Dolphin code.

Language files:

1. 100% translated original file
   The offered language file should be completely translated, manually is preferred.


2. SQL file
   The translated language file should be presented as an SQL file so the new values will be added to a database. This will prevent cases of missing the language file itself.


3. UTF formatted
   Dolphin is set up to work with UTF-8 encoding, and to avoid errors which may appear as different symbols the language file should be written in UTF-8 encoding.


4. International standard
   The language should be marked with international standards marks. Language files should be named the following way: lang-country. Country and dash isn't mandatory. The language name must follow ISO 639-1 (2002) standards and country name must follow ISO 3166 standards.

Templates:

1. Changed Uni template
   The offered template should be your own work with the structural code. The changed colors and pics of the Uni template (Dolphin default template) cannot be uploaded as a product.


2. Copyrighted pictures
   The pictures used for the template design shouldn't be copyrighted. Be careful when choosing pictures for your products.


3. Dolphin original footers
   BoonEx footers should be intact in your template.


4. File changes only
   The template package should be contained completely in the tmpl_templatename folder and consist of this folder only. It shouldn't change or be part of any other files.

Tutorials:

1. Accessible file format
   The offered file should be presented in a format that makes it possible to read it easily without the installation of any additional applications.


2. Completeness
   The product must contain full information and should describe all the nuances of the process described. (should cover the entire installation process).


3. Detailed description
   The tutorial description should contain complete information about its content, which product and product version this file is for, and which program can be used to view it.


4. No hack instructions
   The offered products should provide no information on how to hack BoonEx software: licenses, links, etc.