Redirects to be set before initial import. #17

Activity

1. rianrietveld

   changed the title [-]Redirect to be set before initial import.[/-] [+]Redirects to be set before initial import.[/+] on Sep 22, 2026
2. coffee2code commented on Sep 24, 2026

   

   coffee2code

   on Sep 24, 2026

   Contributor

   More actions

   Redirect are defined in site-specific mu-plugin files that aren't open-sourced. Here's the redirect code that would appear in that file that takes into account the redirects you've specified above. Let me know if I misunderstood your intent.

   The only content note I have is that test-for-web-accessibility subpages are requested to be redirected to best-practices, though there is a best-practices/test-for-web-accessibility page. The code draft below adheres to your original request, but I can change it if need be.

   /**
    * Redirects handbook URLs.
    *
    * Notes:
    * - This is contingent on the handbook using the 'handbook' post type (i.e. a single-handbook site).
    * - Currently only redirects handbook pages within the same handbook.
    */
   add_action( 'template_redirect', function() {
   	$handbook_page = get_query_var( 'handbook' );
   
   	// Only redirect handbook pages.
   	if ( ! $handbook_page ) {
   			return;
   	}
   
   	$redirect = null;
   
   	switch ( $handbook_page ) {
   		case 'best-practices/accessibility-overview':
   		case 'best-practices/quick-start-guide':
   		case 'best-practices/training-and-resources':
   		case 'content':
   		case 'content/accessible-pdfs':
   		case 'content/good-link-texts':
   		case 'content/link-destinations':
   		case 'content/readability':
   		case 'content/using-headings-in-content':
   		case 'markup':
   		case 'markup/aria-landmarks':
   		case 'markup/design-patterns':
   		case 'markup/heading-structure-in-theme-development':
   		case 'markup/semantic-html':
   		case 'markup/tables':
   		case 'markup/web-forms':
   		case 'markup/wp-a11y-speak':
   		case 'plugin-accessibility':
   		case 'test-for-web-accessibility/test-for-web-accessibility-content':
   		case 'test-for-web-accessibility/test-for-web-accessibility-design':
   		case 'test-for-web-accessibility/test-for-web-accessibility-frontend-code':
   		case 'which-tools-can-i-use':
   		case 'which-tools-can-i-use/education-opportunities':
   		case 'which-tools-can-i-use/other-plugins-to-improve-accessibility':
   		case 'which-tools-can-i-use/useful-tools':
   		case 'which-tools-can-i-use/wp-accessibility-plugin':
   			$redirect = 'best-practices';
   			break;
   		case 'about/accessibility-improvement-project':
   			$redirect = 'get-involved/tickets-tasks-reports';
   			break;
   		case 'get-involved/site-feedback-guide':
   			$redirect = 'get-involved/audits-and-testing';
   			break;
   		case 'markup/core-accessibility-standards':
   		case 'which-questions-should-you-ask':
   		case 'which-themes-can-you-use':
   			$redirect = 'accessibility-guidelines';
   			break;
   		case 'markup/skip-links':
   			$redirect = 'best-practices/skip-links';
   			break;
   		case 'markup/the-css-class-screen-reader-text':
   			$redirect = 'best-practices/the-css-class-screen-reader-text';
   			break;
   		default:
   			$redirect = null;
   	}
   
   	if ( $redirect ) {
   		wp_safe_redirect( home_url( '/handbook/' . $redirect . '/' ), 301 );
   		exit;
   	}
   } );
3. rianrietveld commented on Sep 25, 2026

   

   rianrietveld

   on Sep 25, 2026

   MemberAuthor

   More actions

   @coffee2code thanks so much for putting this together.

   You are right about the test-for-web-accessibility subpages.

   So for that pages:

   case 'test-for-web-accessibility':
   case 'test-for-web-accessibility/test-for-web-accessibility-content':
   case 'test-for-web-accessibility/test-for-web-accessibility-design':
   case 'test-for-web-accessibility/test-for-web-accessibility-frontend-code':
       redirect = 'best-practices/test-for-web-accessibility';
       break;

   Where does this code live? When the knowledge base on wpaccessibility.org is migrates to developer.wordpress.org this urls need to point to the new pages.
4. coffee2code commented on Sep 30, 2026

   

   coffee2code

   on Sep 30, 2026

   Contributor

   More actions

   @rianrietveld I've added those changes to my copy of the redirect script. Are you saying that those test-for-web-accessibility links will need to redirect to developer.wordpress.org at some point? If so, we may want to consider using a 302 (temporarily moved) redirect response rather than a permanent 301. Are there other such temporary redirects amongst the whole list?

   The code will be in a closed-source mu-plugin, mostly out of convenience and convention. Future redirects can be requested through meta.trac. We could consider putting a copy of the redirects as a script in this repo, but it would be a copy and not one actively used or reference by wordpress.org.

   Also, do you have a desired timeframe for when you'd like the handbook imported and redirects added to production?
5. rianrietveld commented on Oct 1, 2026

   

   rianrietveld

   on Oct 1, 2026

   MemberAuthor

   More actions

   Hey @coffee2code

   Yes, the plan is to move info on wpaccessibility.org to a new section named accessibility on developer.wordpress.org.
   This includes the sections Start with accessibility, Standards and best practice and Test for accessibility.
   And then a 302 redirect, for now, makes sence.

   Having a copy of the redirects as a script in this repo would be very helpful.

   As for the timeframe: as soon as possible.

   Thanks for helping out 🌷
6. rianrietveld commented on Oct 1, 2026

   

   rianrietveld

   on Oct 1, 2026

   MemberAuthor

   More actions

   cc @joedolson 👆
7. coffee2code commented on Oct 20, 2026

   

   coffee2code

   on Oct 20, 2026

   Contributor

   More actions

   The redirects were implemented for the handbook in production just after the initial import of the handbook from GitHub on 2026-10-13. And #22 adds a copy of the redirects to this repo for future reference. These should close out this issue.
8. rianrietveld commented on Oct 20, 2026

   

   rianrietveld

   on Oct 20, 2026

   MemberAuthor

   More actions

   Thanks @coffee2code 🌷 #22 is merged.

   🎉React with 🎉1Reacted by Scott Reilly
9. rianrietveld

   closed this as completedon Oct 20, 2026