Skip to content

Content considerations before initial import #16

Closed

Description

@coffee2code

Here are a few considerations that should at least be acknowledged, and possible changed, prior to the initial import of the handbook onto Make Accessibility Team's P2.

  • Confirm that the following page found in production is deliberately omitted in GitHub: Site Feedback Guide. If so, does it warrant an redirect or is it just gone?
  • about/index.md : Links "focus on accessibility" to https://make.wordpress.org/accessibility/handbook/about/accessibility-improvement-project/, which does not exist in production or in the handbook on GH.
  • Confirm that the slug for the "Accessibility Guidelines" page is changing from "which-questions-should-you-as" to "accessibility-guidelines". (It makes sense, but we'll want to add a redirect.)
  • Inconsistent page title casing in the manifest. Most pages only capitalize the first letter and proper names, some capitalize all (or most) words. I'd lean towards the former (affects both the title in the manifest and in each page's markdown):
    • "Profile Badges" → "Profile badges"
    • "Accessibility Audits and testing" → "Accessibility audits and testing"

Presumably all content differences between the current handbook and the GH handbook are intentional, so I haven't gone so far as comparing the content.

Nothing above is a blocker, but they are worth addressing ahead of time (if needed). Any needed redirects would be the most beneficial thing to have sorted before importing.

Activity

  1. rianrietveld commented on Sep 22, 2026

    @rianrietveld
    Member

    @coffee2code Thanks for your review 🌷

    Aswering your questions:

    @joedolson did a review on the content itself, so that is good to go.

    I will create a PR for the changes and a new issue with list of redirects. I will close #2 as you know how redirects are done.

  2. self-assigned this
    on Sep 22, 2026
  3. rianrietveld commented on Sep 22, 2026

    @rianrietveld
    Member

    @coffee2code I've created issue #17 with a list of redirects.
    If you tell me how, I can create a PR for this.
    cc @joedolson

  4. coffee2code commented on Sep 24, 2026

    @coffee2code
    ContributorAuthor

    I've replied to #17 with the proposed redirects code. Looks like this particular issue can now be closed. Once the redirects are signed off on, let me know when you'd like me to proceed with importing the handbook.

  5. rianrietveld commented on Sep 25, 2026

    @rianrietveld
    Member

    Thanks @coffee2code for reviewing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions