Documentation-Issue-Tracker icon indicating copy to clipboard operation
Documentation-Issue-Tracker copied to clipboard

Published 20 hours ago • verified publisher icon WordPress

Codex pages still available after migration to DevHub

Open flexseth opened this issue 1 year ago • 4 comments
trafficstars

Issue Description

There are still Codex pages in the wild.

Objective

  • [ ] Identify pages that still exist
  • [ ] Figure out what journey the user took to get here
  • [ ] Audit page for relevant documentation
  • [ ] Provide 301 redirects
  • [ ] Document progress and eventually be done with porting Codex

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

  • 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

Relevant tickets:

  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1442
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1255
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1133
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1096
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1095
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/723
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/624
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/621
    • 👀 @flexseth
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/469
    • 👀 @flexseth
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/427
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/420
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/381
    • 📋 Draft published on DevHub...
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/380
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/370
    • 👋 @jonathanbossenger
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/333
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/331
    • @flexseth
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/330
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/329
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/327
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/161
    • 👀 @jennimckinnon
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/101
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/52

almost related: Broken Links

  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1484 (200, w/some duplicates) @flexseth
  • https://github.com/WordPress/Documentation-Issue-Tracker/issues/1199

Contributing: Understanding User Journeys

If folks are asking about Codex pages, please

  • search to make sure the page in question isn't listed
  • add the link as a comment to this page
  • and ask about their user journey - how did they get to this Codex page? 🤠

@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

  • #1484 redirects, I have a pretty good idea (I think) of how to wrangle the info.

Any and all feedback is welcome!

flexseth avatar Mar 22 '24 13:03 flexseth

Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels.

github-actions[bot] avatar Mar 22 '24 13:03 github-actions[bot]

[Redirect Codex htaccess for subdirectories page] https://github.com/WordPress/Documentation-Issue-Tracker/issues/1515

ASardemann avatar Mar 24 '24 13:03 ASardemann

How To: Migrate from Codex

  • https://make.wordpress.org/docs/handbook/helphub/migrating-articles/

flexseth avatar Mar 25 '24 01:03 flexseth

Codex/Info unavailable after migration to DevHub

  • 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

flexseth avatar Mar 25 '24 19:03 flexseth