DocsWP — WordPress Help

Updating content on WordPress.org

The pages on the WordPress.org main site use patterns to render the page content, so that any changes are tracked in version control. Each pattern is built from page content, so that the editor can be used.

To update a page using the new redesign, you need someone with at least “editor” or “designer” access to the site, and someone from the meta team with commit access to dotorg. They don’t need to be the same person, one person can update the content, while the second syncs & deploys the change.

Make the change in the editor

  1. Edit the page content, using the editor as on any other site. You can use the “Preview in new tab” to see your changes.
  2. Update the page to save your changes. It will not be visible on the front end yet.
  3. On save, an automated action will run to create a pull request with your updates to the version-controlled theme. Go to https://github.com/WordPress/wporg-main-2022/pulls and wait for a PR to appear, it will be called “Content updates from Page Editor” — if there is already a PR, your changes will be added on to it.
  4. Add a comment to the PR explaining your updates.
  5. Someone with a dotorg sandbox should merge and deploy the PR — ask in #meta if you need help.

Deploy the change to the live site (on sandbox)

  1. Merge the automated PR on github
  2. Wait for the actions to finish, specifically the build action.
  3. On a wporg sandbox, sync the changes down into dotorg.svn with the bin/sync/main.sh script.
  4. Deploy wporg.
  5. The change should be live 🎉

Manually build the changes (instructions for reference, it’s better to use the github PR flow)

  1. Sync the updated content to a pattern in the GitHub repository.
    • You’ll need a checkout of wporg-main-2022.
    • Run the generator script
      • If you’re using the Docker environment, start Docker and run yarn wp-env start. Then run yarn build:patterns.
      • If you don’t have yarn, npm run wp-env start and npm run build:patterns should work, but for working on the theme itself (building JS, CSS, etc) yarn is recommended.
      • If you’re using a local environment, cd env and run wp eval-file export-content/index.php page-manifest.json directly.
    • Verify that the changes look correct, and commit.
  2. Push the changes up to GitHub, and wait for the Build action to finish. This will push the commit to the build branch.
  3. On a wporg sandbox, sync the changes down into dotorg.svn with the bin/sync/main.sh script.
  4. Deploy wporg.
  5. The change should be live 🎉