Title: Updating content on WordPress.org
Author: Kelly Choyce-Dwan
Published: March 29, 2023
Last modified: July 15, 2024

---

# Updating content on WordPress.org

[↑ Back to top](https://make.wordpress.org/meta/handbook/about/projects/wordpress-org/updating-content-on-wordpress-org/?output_format=md#wp--skip-link--target)

The pages on the 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/](https://wordpress.org/)
main site use patterns to render the page content, so that any changes are tracked
[in version control](https://github.com/WordPress/wporg-main-2022/commits/trunk/source/wp-content/themes/wporg-main-2022/patterns).
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 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 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](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 deployDeploy Launching code from
    a local development environment to the production web server, so that it’s available
    to visitors. the PR — ask in #meta if you need help.

**Deploy the change to the live site** (on sandbox)

 1. Merge the automated PR on 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/)
 2. Wait for the actions to finish, specifically [the build action](https://github.com/WordPress/wporg-main-2022/actions/workflows/build.yml).
 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](https://github.com/WordPress/wporg-main-2022).
 2.  * 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, CSSCSS CSS
          is an acronym for cascading style sheets. This is what controls the design
          or look and feel of a site., 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.
 3. Push the changes up to GitHub, and wait for [the Build action](https://github.com/WordPress/wporg-main-2022/actions/workflows/build.yml)
    to finish. This will push the commit to the `build` branch.
 4. On a wporg sandbox, sync the changes down into dotorg.svn with the `bin/sync/main.
    sh` script.
 5. Deploy `wporg`.
 6. The change should be live 🎉

First published

March 29, 2023

Last updated

July 15, 2024

[  Previous: WordPress.org](https://make.wordpress.org/meta/handbook/about/projects/wordpress-org/)

[  Next: WordPress.org Navigation](https://make.wordpress.org/meta/handbook/about/projects/wordpress-org/wordpress-org-navigation/)