You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long list of links below under Documentation Issues tracker: Codex
Section of Page with the issue
The entire page needs to be redirected to a relevant DevHub page, if appropriate. If the information is deprecated, it's probably a good idea to add a notice.
Why is this a problem?
If a developer picks up a site that has a piece of legacy code on it, and they want to modernize, support, etc, this code... and the Codex is completely removed... the site will not be easy to work on.
Additionally speaking, if they run into the old Codex in the wild, they may be confused if this info is up to date and run to the support forums. Creating more support tickets.
This process can help to modernize old processes and ways of doing things with WordPress, while also keeping the DevHub to the most healthy standard possible.
Suggested Fix
Log all reports to broken/Codex page issues, and make sure the steps in the first part of this article are taken to
make sure the info is up to date,
deprecated,
or redirected on DevHub
Documentation Issues tracker: Codex
Search Criteria
"migration from Codex"
or had the word "codex" in them
listed in reverse chronological order as of March 22, 2024
Natively import/export - old Codex page has been de-indexed and the content isn't on the new DevHub page. It actually links to a plugin with a paid version. Can't find the link to the WXR standard for future plugin authors
Issue Description
There are still Codex pages in the wild.
Objective
See Suggested Fix for more info
URL of the Page with the Issue
Sample Codex page: Blog by Email
Long list of links below under
Documentation Issues tracker: Codex
Section of Page with the issue
The entire page needs to be redirected to a relevant DevHub page, if appropriate. If the information is deprecated, it's probably a good idea to add a notice.
Why is this a problem?
If a developer picks up a site that has a piece of legacy code on it, and they want to modernize, support, etc, this code... and the Codex is completely removed... the site will not be easy to work on.
Additionally speaking, if they run into the old Codex in the wild, they may be confused if this info is up to date and run to the support forums. Creating more support tickets.
This process can help to modernize old processes and ways of doing things with WordPress, while also keeping the DevHub to the most healthy standard possible.
Suggested Fix
Log all reports to broken/Codex page issues, and make sure the steps in the first part of this article are taken to
Documentation Issues tracker: Codex
Search Criteria
as of March 22, 2024
Relevant tickets:
almost related: Broken Links
Contributing: Understanding User Journeys
If folks are asking about Codex pages, please
@zzap - if you could please add the tag "Tracking Issue" to this ticket, when new URLs are found they can be added here to be fixed.
This is a fairly large undertaking, but having worked on the
redirects, I have a pretty good idea (I think) of how to wrangle the info.
Any and all feedback is welcome!
The text was updated successfully, but these errors were encountered: