Update to /documentation/ didn't redirect PHP and Site-Health Pages

[estelaris]

The link to the pages for PHP and Site-Health in the previous ?support/ site (now /documentation/) need to be updated/redirect?

Pages: ​https://wordpress.org/support/update-php/ and ​https://wordpress.org/support/site-health/

More info: https://meta.trac.wordpress.org/ticket/4004
​https://make.wordpress.org/core/2019/01/14/php-site-health-mechanisms-in-5-1/
​https://github.com/WordPress/wporg-documentation-2022/issues/48

That is all the information I found about these pages.

[dd32]

These pages are "special" as they're translated and available in every locale, eg ​https://de.wordpress.org/support/update-php/ (Even if the locale doesn't have a /support/ site, and the content is translated via GlotPress, not through the /support/ site admin)

It should be updated so as to be presented via /documentation/ but due to the hard-coded page content for translations, it's not as simple as copying the content over.

[ryelle]

The content can be moved over to a pattern in documentation, but those translations won't actually be used since the Rosetta sites use the wporg-support theme. This would cause the content to be duplicated between the two themes, at least until the redesign is rolled out to Rosetta.

Would that work if the redirect only applied to the non-rosetta site?

[dd32]

Would that work if the redirect only applied to the non-rosetta site?

Yep!

Are strings for the Documentation theme even being imported into GitHub anywhere yet? If not, there'll be no immediate duplicate strings to worry about.

The translations can be exported/imported between the projects when the time comes to enable it.

[estelaris]

Replying to dd32:

Are strings for the Documentation theme even being imported into GitHub anywhere yet? If not, there'll be no immediate duplicate strings to worry about.

There are no plans yet to move documentation strings into GH, so if redirects are only applied for non-Rosetta site, can we close this ticket?

[estelaris]

moving this to the GH documentation issue tracker to follow up
[Issue 1446]​https://github.com/WordPress/Documentation-Issue-Tracker/issues/1446