[Monorepo] Netlify to replace pr-review

[spectranaut]

We also want to look to add the follow features to our netlify publications:

• links in the comment from netlify to all specs that were edited by the PR, like: https://deploy-preview-2284--wai-aria.netlify.app/core-aam/ => PR [Monorepo] Netlify to replace pr-review #2242 -- not spending time on this for now. The checks tabs on each PR contains this info
• Can we have some kind of banner/message -- that links from the netlify publication back to the PR it was generated from? Explains what this is a preview of? -- Low priority issue, not planned for now.
• Eventually, we will need successful links between specs generated by the PR instead of links to the editor's drafts
• publish generated respec document (instead of running respec client side)
• relative links to ARIA specs point to netlify preview Editorial: Relative links for PR and branch netlify previews #2473

[daniel-montalvo]

We now have statically-generated PR previews
#2265
All pages changed can be viewed from within the "Checks" tab, for example in https://github.com/w3c/aria/pull/2284/checks/> Netlify > Page changed

[spectranaut]

About Eventually, we will need successful links between specs generated by the PR instead of links to the editor's drafts -- If, for core-aam, we add the ED links like this:

  ariaSpecURLs: {
    ED: "../index.html",
    CR: "https://w3c.github.io/aria/",
    CRD: "https://w3c.github.io/aria/",
    PR: "https://www.w3.org/TR/wai-aria/",
    REC: "https://www.w3.org/TR/wai-aria/",
  },
  accNameURLs: {
    ED: "../accname/index.html",
    CR: "https://w3c.github.io/accname/",
    CRD: "https://w3c.github.io/accname/",
    PR: "https://www.w3.org/TR/accname-1.2/",
    REC: "https://www.w3.org/TR/accname-1.2/",
  },

It works in PR preview, which you could see before I realized w3c.github.io/core-aam editor draft would be broken: #2298

So maybe we really do need to set up all the w3c.github.io/* to directed back to this repository. Then if we do this for all the specs, the links will be correct in PR preview... right...?

[daniel-montalvo]

@spectranaut @pkra @jnurthen and all.

I have followed an approach similar to @spectranaut comments above in https://github.com/daniel-montalvo/aria

The build process now has a bash script that replaces specStatus with "unofficial" and then includes the unofficial keys for the resolveReferences function to generate relative links in the PRs.

For a prototype of how this could work, see
https://staging-aria.netlify.app
and add / to get to the other specs as desired.

I am using the Netlify production context for now because this is just a test. If we are happy with this approach, I will adjust the main ARIA netlify configuration file accordingly so that this only runs in PRs.

[pkra]

@daniel-montalvo I thought #2325 and #2386 had fixed cross references to link within PRs but on #2416 in https://deploy-preview-2416--wai-aria.netlify.app I find ~5000 links starting with https://w3c.github.io/aria/#. Should I open a new issue?

[daniel-montalvo]

Daniel to have a look at links that take to github.io

An example is list item.