APG Redesign

[howard-e]

Overview

Given that w3c/aria-practices#2169 has been approved and merged, we'd like to move forward with adding the technical elements required to support the APG's redesign and also enabling it to be a 'resource' of WAI. See WAI Website Manual and specifically WAI Website Manual - Technical Information for more context. We intend to use this repository as a content transformer and to also hold the redesign content as shown at http://wai-aria-practices.s3-website-us-east-1.amazonaws.com.

How deploys will work

The diagram displays that when the production branch for w3c/aria-practices is updated, a wai-trigger-deploy workflow is triggered, which in turn triggers a deploy workflow action on w3c/wai-aria-practices. deploy is responsible for retrieving the latest content from w3c/aria-practices, updating the content files and pushing it back to the repository's production branch, which in turn triggers a Netlify site update.

How pull requests will work

The diagram displays that when a PR is submitted or updated on w3c/aria-practices, the wai-trigger-pr workflow is triggered, which in turn triggers a pr-create workflow action on w3c/wai-aria-practices. This action will create (or update) a generated PR branch on w3c/wai-aria-practices, update the Netlify deploy preview URL, retrieve the Netlify deploy URL preview and update the top comment of the triggering PR from w3c/aria-practices. The diagram also displays that when a PR on w3c/aria-practices is closed (or merged), or the branch is deleted, the related PR and branch is also removed on w3c/wai-aria-practices. This is done by a wai-trigger-cleanup workflow on w3c/aria-practices triggering a remove-branch workflow action on w3c/wai-aria-practices.