Title: docs – Make WordPress Test

---

#  Tag Archives: docs

 [  ](https://profiles.wordpress.org/sirlouen/) [Manuel Camargo](https://profiles.wordpress.org/sirlouen/)
2:29 pm _on_ September 30, 2025     
Tags: docs, test docs   

# 󠀁[The Test Handbook Overhaul](https://make.wordpress.org/test/2025/09/30/the-test-handbook-overhaul/)󠁿

For several meetings, one of the topics that has been repeatedly coming back and
forth is the idea of updating some Test Handbook pages, which have been stalling
a bit for a fairly long time, and it’s good to keep them freshly updated with the
last decisions that have been coming from the latest meetings, especially regarding
certain topics like the new testing protocols.

 1. [Future-Proofing Docs Changes](https://make.wordpress.org/test/tag/docs/?output_format=md#future-proofing-docs-changes)
 2. [Protocol to mirror the current docs with the tracker](https://make.wordpress.org/test/tag/docs/?output_format=md#protocol-to-mirror-the-current-docs-with-the-tracker)
 3. [Addressing Future Improvements to the Handbook](https://make.wordpress.org/test/tag/docs/?output_format=md#addressing-future-improvements-to-the-handbook)

## Future-Proofing Docs Changes

It is important that we address this as soon as possible to keep our processes up
to date and efficient. More specifically, in the last meeting, [@krupajnanda](https://profiles.wordpress.org/krupajnanda/)
commented that maybe we should be updating based on the [Test Handbook GitHub repo](https://github.com/WordPress/test-handbook).
All current active Test Team members found value in this change and agreed on making
it possible.

Furthermore, we could also agree that working in the GitHubGitHub GitHub is a website
that offers online implementation of git repositories that 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 by the repository owner. [https://github.com/](https://github.com/)
repo will let us have a perfect log of changes and reasons behind changes, plus 
having everything better documented than just making changes directly on the Test
blog.

After taking a more in-depth look, it seems to be a great idea to start from that
point, and from there, we will be taking the next steps to make this happen.

Working in GitHub also helps us share the responsibility of maintaining the team
pages with other Test contributors, and not only the Test Team members locating 
issues and helping fix them.

## Protocol to mirror the current docs with the tracker

First and foremost, we need to ensure that all existing documentation is accurately
mirrored in the tracker to maintain consistency and track progress effectively. 
There was an attempt made 2 or 3 years ago, but the docs have changed partially,
and not all the docs were fully mirrored back then. For the mirror sync to take 
place, all current docs in the blog must be removed first so they can be reloaded
with the sync pluginPlugin A plugin is a piece of software containing a group of
functions that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written in
the PHP programming language and integrate seamlessly with WordPress. These can 
be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party.. We need to make sure with precision
that the docs in the tracker are identical to the docs in the current handbook. 
We will have time to update them afterward, but first, the mirror should be as identical
as possible. This task is not small and will take the following steps:

 1. First, we need to check which docs remain the same.
 2. Second, we have to add the missing docs with the best similar format possible.
 3. Third, we must review all the assets (images, videos, etc.) and links.
 4. Finally, we will have to make the table of contents manifest for the sync.

Collaboration and careful attention to detail will be essential throughout this 
process to ensure a smooth and accurate synchronization. A [GitHub project](https://github.com/orgs/WordPress/projects/263)
will be created to track all the tasks in those four steps mentioned, assigned to
each collaborator. Once we can confirm that the mirror is done, we can move into
the next section.

## Addressing Future Improvements to the Handbook

After the first step has been accomplished, we will need to execute the sync. For
this process, [@SirLouen](https://profiles.wordpress.org/sirlouen/) will be contacting
the MetaMeta Meta is a term that refers to the inside workings of a group. For us,
this is the team that works on internal WordPress sites like WordCamp Central and
Make WordPress. team, and in collaboration with them, we will enable the sync process.

Once we have the syncing up, we will be able to handle improvements easily with 
the GitHub Issue Tracker. Making decisions on what to change and what not to will
be an important factor in how to handle this. But ideally, we should continue with
the current format:

 1. Commenting on and addressing these things in our meetings
 2. Proposing a PR
 3. After some validations by the Test Team, they will be added to the Handbook.

Test contributors will have the ability to create GitHub PRs on issues in their 
time and convenience and to offer suggestions using GitHub Issues, and these are
what will then be discussed in the meeting on a certain day or in a certain meeting
to ensure proper planning and transparency. These issues will then be sorted by 
the Test team to see which ones meet the criteria.

Test Team members will have write access to the repository, so they will be able
to accept revisionsRevisions The WordPress revisions system stores a record of each
saved draft or published update. The revision system allows you to see what changes
were made in each revision by dragging a slider (or using the Next/Previous buttons).
The display indicates what has changed in each revision., but still, all changes
should undergo a meeting process before approval. Proposals should go into either
a GitHub issue or a GitHub PR and be brought into the meeting. This approach will
help maintain clarity, ensure quality control, and keep everyone aligned on updates.

_Props to [@mosescursor](https://profiles.wordpress.org/mosescursor/), [@nikunj8866](https://profiles.wordpress.org/nikunj8866/),
and [@krupajnanda](https://profiles.wordpress.org/krupajnanda/) helping review this
article and offering feedback._

[#docs](https://make.wordpress.org/test/tag/docs/), [#test-docs](https://make.wordpress.org/test/tag/test-docs/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2025%2F09%2F30%2Fthe-test-handbook-overhaul%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
6:56 pm _on_ August 20, 2021     
Tags: [build-test-tools ( 34 )](https://make.wordpress.org/test/tag/build-test-tools/),
docs   

# 󠀁[[Call for volunteeers] Audit and Update Testing Instructions across the Make sites](https://make.wordpress.org/test/2021/08/20/call-for-volunteeers-audit-and-update-testing-instructions-across-the-make-sites/)󠁿

In the summer of 2021, the Test team started meeting again for chats, triage sessions,
and scrubs. One of the things that keeps coming up is the need to have clear instructions
for testing.

They are scattered across many Make websites, they are not all kept up-to-date with
changes in the different environments they mention, they not always link to existing
documentation and, in some cases, they link to pages that no longer exist.

This makes it more difficult for new contributors to join the sessions and actively
participate in the team initiatives.

During [one of the meetings](https://make.wordpress.org/test/2021/08/19/test-team-chat-summary-17-august-2021/),
the attendees agreed that having good documentation is a priority to welcome new
contributors.

## Goals

 1. Make sure all testing instructions for the most commonly used environments used
    to test WordPress CoreCore Core is the set of software required to run WordPress.
    The Core Development Team builds WordPress. are updated and unified, across the
    Make websites.
 2. Review the existing Test team handbook: edit, remove and add pages.

## Process

At this stage, I am focusing on the first goal: review the testing instructions,
simplify if possible, and make sure they are all up-to-date.

The process I have in mind is:

 1. Create a [spreadsheet](https://docs.google.com/spreadsheets/d/1D4Q2_P_FriSxj19P2HIso81s2SZf5RcUVFaTUe12cuk/edit?usp=sharing)
    with all the pages that mention testing in the:
 2.  a. Make Hanbooks for: 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), Core, Design, Test
     b. `wordpress-develop`
     c. TracTrac Trac is the place where contributors create issues for bugs or feature
        requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).
 3. Post in the team-reps SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
    The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
    Channel a call for volunteers, so all teams involved can coordinate
 4. Create or edit instructions for each environment and cross-link if necessary.
 5. Update people in the team-reps every X weeks about the progress done (to be decided
    with the group of volunteers that will work on this initiative).
 6. Future > Act swiftly when something changes, so ideally instructions are never 
    out of date. This is quite hard without version control in our handbooks, but we’ll
    cross this bridge when we get here 😉

Here is the spreadsheet: https://docs.google.com/spreadsheets/d/1D4Q2_P_FriSxj19P2HIso81s2SZf5RcUVFaTUe12cuk/
edit?usp=sharing

Then we can move on to goal number 2 (or another group of people can work on that
simultaneously).

Wanna help? Comment in this blog post with your Slack username and we can start 
working 🙂

Thank you!

_Props to [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) and 
[@mai21](https://profiles.wordpress.org/mai21/) for peer review._

[#build-test-tools](https://make.wordpress.org/test/tag/build-test-tools/), [#docs](https://make.wordpress.org/test/tag/docs/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F08%2F20%2Fcall-for-volunteeers-audit-and-update-testing-instructions-across-the-make-sites%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
5:59 pm _on_ February 19, 2021     
Tags: [core-editor ( 12 )](https://make.wordpress.org/test/tag/core-editor/),
docs, [fse-answers ( 7 )](https://make.wordpress.org/test/tag/fse-answers/), [fse-outreach-program ( 110 )](https://make.wordpress.org/test/tag/fse-outreach-program/)

# 󠀁[FSE Program: Answers about the FSE project](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-the-overall-project/)󠁿

This post is part of a series that provides answers to [questions gathered in early February](https://make.wordpress.org/test/2021/02/02/fse-program-bring-your-questions/).
Thank you to everyone who submitted a question so our knowledge can grow together!
Each post will help provide foundational knowledge for future documentation efforts,
and future calls for questions in the coming months. 

**All posts in this series:**

 * [Answers about the FSE project](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-the-overall-project/)(
   this post)
 * [Answers about templates](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-templates/)
 * [Answers about themes](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-themes/)
 * [Answers about restricting access & functionality](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-restricting-access-functionality/)
 * [Answers about general functionality](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-general-functionality/)

**The focus of this post: **

This post focuses on questions related to the overall project, including the role
of 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.
based widgets & navigation screens, the why of FSE, and how easy it will be to use
for a beginner.

 [Continue reading →](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-the-overall-project/#more-5691)

[#core-editor](https://make.wordpress.org/test/tag/core-editor/), [#docs](https://make.wordpress.org/test/tag/docs/),
[#fse-answers](https://make.wordpress.org/test/tag/fse-answers/), [#fse-outreach-program](https://make.wordpress.org/test/tag/fse-outreach-program/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F02%2F19%2Ffse-program-answers-about-the-overall-project%2F%23respond&locale=en_US)