Call for maintainers: Theme Unit Test

The Theme Unit Test is a widely known XML file with test content for WordPress websites. Theme authors and reviewers use this file to test various content types, including blocks, classic content, sound, video, images, comments, and menus.

As my focus is moving more towards accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and full site editing, I do not have the capacity to keep the file up to date or respond to issues and pull requests on GitHub in a timely manner.

Except for typos, the last substantial update to the theme unit test was July 3, 2020.

Because of the lack of updates, some blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. content no longer matches what you would get if you manually created new blocks in the editor. 

The demo content has been available since 2011 and is an important tool for theme authors. For it to remain useful, it needs to be updated more regularly, and your help is wanted.

What does a maintainer do?

  • Triage issues, open issues, and create pull requests on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository.
  • Update the XML file when there are block markup changes (Keeping the old markup examples is still important for testing).
  • Update the XML file to include new major blocks.
  • Keep the codex page up to date.
  • Plan for the future and how the content and format can be improved.

What skills do I need to become a maintainer?

  • To update the file, you need to have basic knowledge of XML and the structure of the content exported and imported from WordPress.
  • Have intermediate experience with the block editor, and stay up to date with block markup changes.
  • You need a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account to be able to update the codex page.
  • Intermediate knowledge of GitHub and working with issues and pull requests.

I want to help, who do I contact?

Leave a comment on this post if you would like to help or if you have any questions.