Thanks for adding info at the Plugin API page!

• WordPress Documentation Team - Know who is in charge and who to turn to
• Guidelines - The heavenly handbook of Codex rules.
• Styles - Documentation of the general styles of the Codex — please follow these so pages look well together.
• Sandbox - Your experimental playground
• Contributing - How to help out at the Codex
• Editing - How to layout and design a Codex page
• Codex Tasks - Things needing to be done and sign up list

Discussions on the Codex

Discussions on the Codex and Wp-docs mailing list are restricted to topics related to writing WordPress documentation. To post a question about information on an article in the Codex, use the Discussion Tab at the top of the article's page. To post a question to an individual Codex user, visit their User Page and post the question in their Discussion page. Answers will be posted on your User Discussion page. Sign all comments and discussions with four tildes (~) and it will display your name and time with a link to your User Page like this:
Fred Smith 03:07, 10 Apr 2014 (UTC)

Again, welcome and let us know how we can help you help us on the WordPress Codex.

Carthik ‹ ℂ › Talk 14:39, 11 May 2005 (UTC)

The Plugin Hooks

Hi Davepar,

Good work on the Plugin API hooks :) I just thought of a couple of things real quick:

1. It may not be possible to generate examples for each of the hooks, since quite a few "action" hooks only signify some sort of activity on the blog. Without examples, a particular hook page will be pretty short. So may I suggest reducing the number of sub-pages? You could have the hooks/filters categorized by their functionality, or the data they operate on, or both.
2. Please note that generally add_action and apply_filter are essentially the same, but functionally, we would like to make a distinction between the two, as far as possible - this is just a note for when you get around to doing these...
3. "Used to change the appearance of the category list... " (for example) may convey the wrong impression, as in, someone might confuse a hook for a function that does something by itself. I would think that using something like "Operations on xyz(some sort of data) can be carried out by using hook foobar (for a filter hook)" or "This hook signifies that all the initiation operations, including loading the plugins have been carried out (to take the example of the "init" action hook)". In short, specifying what the hook signifies, or lets the plugin author access/modify might be better. I only say this since you are starting out, and it might be easier to change things now, that later.

Of course, the above are only my subjective opinions, please let me know what you think of them.

Again, thanks a lot for pitching in!

Carthik ‹ ℂ › Talk 04:16, 14 May 2005 (UTC)

We're anxious to "do" something with these and want to make sure you are done with them and that they are ready. Please let me know as soon as possible. Thanks! Lorelle 14:31, 28 Jul 2005 (UTC)