Title: Standards for Hacks
Last modified: August 18, 2016

---

# Standards for Hacks

 *  [NuclearMoose](https://wordpress.org/support/users/nuclearmoose/)
 * (@nuclearmoose)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/standards-for-hacks/)
 * Oooo, sounds all official and everything, eh? Well, right now, it’s not. As part
   of the documentation effort, and the overall effort to create a great product
   like WordPress and to add value to WP through extensions, hacks, mods, plug-ins,
   or whatever you choose to call them, I have some proposals for discussion purposes.
   For the sake of making this post less wordy, I’m going to call everything a “
   mod.”
    Items which are already defined by the developers: 1. [Coding style](http://wordpress.org/docs/developer/#coding-style)
   rules have been published and all mods must adhere to this style. 2. Refer to
   the [Hack Guidelines](http://wordpress.org/support/10/341) for other information.
   My proposals: 3. All coding must validate to the minimum XHTML standard that 
   WP validates to, and that is XHTML Transitional. 4. Unless otherwise stated by
   the developers, individual mod support falls on the mod developer with the help
   of the WP community members who are willing and able to help. 5. Mods must be
   documented fully, including date, author, version number, target WP version, 
   and mod Title. Instructions should be included on how to install and implement
   the code. The documentation should also include a listing of the features the
   mod offers. What I am looking for here is a mod product that would stand up to
   the standard which WP will be setting for itself. 6. It would be desirable to
   have mod authors host a page on their own sites where community members could
   obtain the necessary code and documentation. 7. WordPress is published under 
   the [GNU General Public License](http://www.gnu.org/copyleft/gpl.html) and authors
   of all mods should document fully what copyright restrictions they wish to place
   on the code submitted as mods. I think that this is basically it, in terms of
   documentation stuff. I invite your comments and ideas. Thanks… Craig.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [Laughinglizard](https://wordpress.org/support/users/laughinglizard/)
 * (@laughinglizard)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/standards-for-hacks/#post-29245)
 * How about a pre-defined form for hack-authors to fill out and include with the
   hack? It would contain the staples such as author, webpage, versions affected,
   instructions and other desireables.
 *  [alexkingorg](https://wordpress.org/support/users/alexkingorg/)
 * (@alexkingorg)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/standards-for-hacks/#post-29247)
 * When I get the Hacks section up and running, there will be a submission form 
   that will capture this data. And naturally, the system will be running WordPress.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Standards for Hacks’ is closed to new replies.

 * 2 replies
 * 3 participants
 * Last reply from: [alexkingorg](https://wordpress.org/support/users/alexkingorg/)
 * Last activity: [22 years, 4 months ago](https://wordpress.org/support/topic/standards-for-hacks/#post-29247)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics