PR Publication Prep

[egekorkan]

This Pull Request creates all the static files needed for the publication

• CSS rules: Pass
• Link Checker: Many false positives. It mentions broken fragments or internal server errors but I do not see them if I go to the link myself.
• Pubrules: Warnings. One important one says "If it is the intention to incorporate new features in future updates of the Recommendation, please make sure to identify the document as intending to allow new features.". I think we should add this. Any opinions?

Note: these links are not necessarily up to date since they use the commit hash.

Changes I had to do to index.html:

• comment out linking to atrisk.css
• change IETF links to datatracker.ietf instead of tools.ietf
• fix some HTML fragments in the links (IETF, OpenAPI, i18n)
• change schema.org extensions to use HTTPS (i.e. http://schema.org to https://schema.org)
• Remove at risk paragraphs in the beginning of the privacy and security sections.
• Add recent changes section

---

Preview | Diff

[egekorkan]

Call of 07.06:

• New feature note should be added

[egekorkan]

We agree to merge this PR.

[mmccool]

@egekorkan Did you run HTML tidy also? I did this in the past for CR publication and it caught a lot of HTML errors (fixes for which I then merged back into the main doc, but more may have been introduced since).

[egekorkan]

@egekorkan Did you run HTML tidy also? I did this in the past for CR publication and it caught a lot of HTML errors (fixes for which I then merged back into the main doc, but more may have been introduced since).

Yes! :) I have fixed quite some more beforehand as well