Add Action and Filter Reference Documents to DevHub

[jonathanbossenger]

What is the new page you are requesting?

Two new pages based on the Codex pages on the Action Reference list and Filter Reference list

How will this new page help you?

These two pages are valuable reference documents for WordPress developers, as it allows a developer to both determine the correct hook to use, based on when the hook is executed. It also provides a great high-level overview of what each hook does and then links to each specific hook's DevHub doc.

Additional notes

It has been suggested that both pages should be added to the Common APIs handbook.

Once these pages have been added, they can be updated with any newly added hooks, as well as fixing the broken links that currently exist on each page.

[jonathanbossenger]

I'd appreciate it if someone can a) assign me to this ticket, and b) help me with getting access to DevHub, to be able to add these pages, and get them updated.

[jonathanbossenger]

Shoot, I need to finish this up...

[jonathanbossenger]

Hi folks.

In light of the recent changes to the Codex, I have submitted the two drafts (Action Reference and Filter Reference) to be published to the common APIs section of the handbook.

I also created a parent page (Hooks) for these two pages, so that once the references are published, we can nest the two reference pages under Hooks.

At the same time, we should probably update the links at the bottom of the Hooks page in the Plugin developer handbook.

[jonathanbossenger]

Noting that most of the links on the new pages are broken, probably because the codex pages don't exist anymore.

[flexseth]

Related work is going on here @jonathanbossenger

• [Common APIs handbook] Missing links on Action Reference article #1484

Working on it. It's a lot of links :)

Tagging for tracking/to be able to submit to review/close when finalized.

[flexseth]

Noting that most of the links on the new pages are broken, probably because the codex pages don't exist anymore.

This is correct. To a certain, perhaps unfortunate degree.

That said, we can link directly to the Inline Documentation of the code which should help advanced users. Or if possible, update the DocBlocks to reflect necessary info to pull in the reference info.

I'm not 100% sure exactly what the best approach is yet for this, but should figure it out while working on the various broken links in the Common APIs Handbook post.