chore: Avoid github page generation for xml spec (#1248)

kesara · web-flow · commit 34eefa37db71 · 2025-06-26T16:37:51.000+12:00
* build: Remove docs-publish GHA

* docs: Update references to github pages

* chore: Run yestests (pre-changes)

* chore: Run yestests (post-changes)
diff --git a/.github/workflows/docs-publish.yml b/.github/workflows/docs-publish.yml
diff --git a/README.md b/README.md
@@ -26,7 +26,9 @@
 
 ### Introduction
 
-The [IETF] uses a specific format for the standards and other documents it publishes as [RFCs], and for the draft documents which are produced when developing documents for publications. There exists a number of different tools to facilitate the formatting of drafts and RFCs according to the existing rules, and this tool, **xml2rfc**, is one of them. It takes as input an xml file that contains the text and meta-information about author names etc., and transforms it into suitably formatted output. The input xml file should follow the grammars in [RFC7749] *(for v2 documents)* or [RFC7991] *(for v3 documents)*. Note that the grammar for v3 is still being refined, and changes will eventually be captured in the [bis draft for 7991]. Changes not yet captured can be seen in the xml2rfc source [v3.rng], or in the [documentation xml2rfc produces] with its `--doc` flag.
+The [IETF] uses a specific format for the standards and other documents it publishes as [RFCs], and for the draft documents which are produced when developing documents for publications. There exists a number of different tools to facilitate the formatting of drafts and RFCs according to the existing rules, and this tool, **xml2rfc**, is one of them. It takes as input an xml file that contains the text and meta-information about author names etc., and transforms it into suitably formatted output. The input xml file should follow the grammars in [RFC7749] *(for v2 documents)* or [RFC7991] *(for v3 documents)*.
+
+[RFCXML vocabulary reference] is available at [authors.ietf.org].
 
 **xml2rfc** provides a variety of output formats. See the command line help for a full list of formats. It also provides conversion from v2 to v3, and can run the [preptool] on its input.
 
@@ -129,9 +131,8 @@ The initial build may take time because it downloads all required fonts as well.
 [RFCs]: https://www.rfc-editor.org/
 [RFC7749]: https://www.rfc-editor.org/info/rfc7749
 [RFC7991]: https://www.rfc-editor.org/info/rfc7991
-[bis draft for 7991]: https://datatracker.ietf.org/doc/draft-iab-rfc7991bis/
-[v3.rng]: xml2rfc/data/v3.rng
-[documentation xml2rfc produces]: https://ietf-tools.github.io/xml2rfc/
+[RFCXML vocabulary reference]: https://authors.ietf.org/en/rfcxml-vocabulary
+[authors.ietf.org]: https://authors.ietf.org/
 [preptool]: https://www.rfc-editor.org/info/rfc7998
 [WeasyPrint]: https://weasyprint.org/
 [WeasyPrint Docs]: https://doc.courtbouillon.org/weasyprint/stable/first_steps.html
diff --git a/pyproject.toml b/pyproject.toml
@@ -42,7 +42,7 @@ homepage = "https://github.com/ietf-tools/xml2rfc"
 source = "https://github.com/ietf-tools/xml2rfc"
 changelog = "https://github.com/ietf-tools/xml2rfc/blob/main/CHANGELOG.md"
 releasenotes = "https://github.com/ietf-tools/xml2rfc/releases"
-documentation = "https://ietf-tools.github.io/xml2rfc/"
+documentation = "https://authors.ietf.org/en/rfcxml-vocabulary"
 issues = "https://github.com/ietf-tools/xml2rfc/issues"
 
 [project.optional-dependencies]
diff --git a/tests/valid/docfile.html b/tests/valid/docfile.html
@@ -369,7 +369,7 @@ <h2 id="name-introduction">
 <p id="section-1-4">
        For an introduction to the v3 schema, with suggestions on how to transition from v2, see <span>[<a href="#INTRO-TO-V3" class="cite xref">INTRO-TO-V3</a>]</span>.<a href="#section-1-4" class="pilcrow">¶</a></p>
 <p id="section-1-5">
-       The latest version of this documentation is available in HTML form at <span><a href="https://ietf-tools.github.io/xml2rfc/">https://ietf-tools.github.io/xml2rfc/</a></span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
+       The RFCXML vocabulary reference is available at <span><a href="https://authors.ietf.org/en/rfcxml-vocabulary">https://authors.ietf.org/en/rfcxml-vocabulary</a></span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
 <p id="section-1-6">
             This documentation applies to xml2rfc version 3.29.0.<a href="#section-1-6" class="pilcrow">¶</a></p>
 </section>
diff --git a/tests/valid/manpage.txt b/tests/valid/manpage.txt
@@ -51,8 +51,8 @@ Table of Contents
    For an introduction to the v3 schema, with suggestions on how to
    transition from v2, see [INTRO-TO-V3].
 
-   The latest version of this documentation is available in HTML form at
-   https://ietf-tools.github.io/xml2rfc/.
+   The RFCXML vocabulary reference is available at
+   https://authors.ietf.org/en/rfcxml-vocabulary.
 
    This documentation applies to xml2rfc version 3.29.0.
 
diff --git a/xml2rfc/templates/doc.yaml b/xml2rfc/templates/doc.yaml
@@ -2096,8 +2096,8 @@ Introduction:
       the v3 schema, with suggestions on how to transition from v2,
       see <xref target="INTRO-TO-V3"/>.
 
-    - The latest version of this documentation is available in HTML form
-      at <eref target="https://ietf-tools.github.io/xml2rfc/"/>.
+    - The RFCXML vocabulary reference is available at
+      <eref target="https://authors.ietf.org/en/rfcxml-vocabulary"/>.
 
 Options:
 
