Orcid WordPress Homepage Deployment

The purpose of this repository is to provide a straightforward method for both technical and non-technical users to deploy a clone of a WordPress post from https://info.qa.orcid.org/

Homepage QA Deploy

Deploy the info.qa.orcid.org page on qa.orcid.org:

• Navigate to Homepage QA Deploy
• Click on "Run workflow"
• Select Create a versioned artifact? = false and select the WordPress post that needs to be deployed (default is 25422)

Homepage PROD Deploy

1. Before deploying it to prod run a QA release that will create a versioned artifact

   • Navigate to Homepage QA Deploy
   • Click on "Run workflow"
   • Select Create a versioned artifact? = true and select the Prod WordPress post that needs to be deployed (default is 25422)
   • The created artifact is now published on qa.orcid.org. Please make sure with your team that this is approved for production before continuing.

2. Deploy the version of this artifact to production

   • Navigate to Homepage PROD Deploy
   • Click on "Run workflow"
   • And run the latest version displayed on the (release list page) .
   • The release will occur in three stages: a release to QA (for a final review), a release to the production-fallback machine, and a release to the production machine.
   • Before the fallback-production and production releases, you will be asked to review the previous release. You will need to approve this to continue. As show on the following image:
   • 

3. Document the date this release version was put up on production

   • Navigate to the release list version, click "Edit," and add a note about the release date for the production version. This information will provide better context for identifying the last stable version if a rollback is necessary.

Rollback Deployment

• Navigate to Homepage PROD Deploy
• Click on "Run workflow"
• And run the version you want to deploy to production (see the full list on versioned artifacts apps)

Developers

Cloning WordPress Locally:

Running the following command will run the cloning process on your local environment (This won't deploy to S3, commit, or do GitHub releases)

export GITHUB_OUTPUT="./dist/output"     
export GITHUB_STEP_SUMMARY="./dist/summary"
python3 wordpress-cloning-main.py STAGE 25422 orcidstaging fb8dd998 --dry-run

Are you adding a new CSS stylesheet to WordPress?

If you add a new stylesheet to WordPress, you will need to update the file wordpress-cloning-css-script.py. This will make the cloning script to include the new stylesheet in the css output file.

Are you adding a new JS stylesheet to WordPress?

If you add WordPress pluggin or new JS file that needs to be clone, you will need to update the file wordpress-cloning-js-script.py.