Use :rfc: role

Author: dukecat0

source/overview.rst

@@ -231,7 +231,7 @@ guides:
 * `Kivy <https://kivy.org/>`_
 * `Beeware <https://pybee.org/>`_
 * `Brython <https://brython.info/>`_
-* :py:module:`Flexx <flexx:flexx>`
+* `Flexx <https://flexx.readthedocs.io/en/latest/>`_
 
 If you are *not* interested in using a framework or platform, or just
 wonder about some of the technologies and techniques utilized by the

source/specifications/core-metadata.rst

@@ -240,8 +240,7 @@ Historically, PyPI supported descriptions in plain text and `reStructuredText
 (reST) <https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html>`_,
 and could render reST into HTML. However, it is common for distribution
 authors to write the description in `Markdown
-<https://daringfireball.net/projects/markdown/>`_ (`RFC 7763
-<https://datatracker.ietf.org/doc/html/rfc7763>`_) as many code hosting sites render
+<https://daringfireball.net/projects/markdown/>`_ (:rfc:`7763`) as many code hosting sites render
 Markdown READMEs, and authors would reuse the file for the description. PyPI
 didn't recognize the format and so could not render the description correctly.
 This resulted in many packages on PyPI with poorly-rendered descriptions when
@@ -275,10 +274,8 @@ Other parameters might be specific to the chosen subtype. For example, for the
 specifying the variant of Markdown in use (defaults to ``GFM`` if not
 specified). Currently, two variants are recognized:
 
-- ``GFM`` for `Github-flavored Markdown
-  <https://datatracker.ietf.org/doc/html/rfc7764#section-3.2>`_
-- ``CommonMark`` for `CommonMark
-  <https://datatracker.ietf.org/doc/html/rfc7764#section-3.5>`_
+- ``GFM`` for :rfc:`Github-flavored Markdown <7764#section-3.2>`
+- ``CommonMark`` for :rfc:`CommonMark <rfc7764#section-3.5>`
 
 Example::
 

source/specifications/declaring-project-metadata.rst

@@ -157,7 +157,7 @@ meaning is open to interpretation.
 These fields accept an array of tables with 2 keys: ``name`` and
 ``email``. Both values must be strings. The ``name`` value MUST be a
 valid email name (i.e. whatever can be put as a name, before an email,
-in `RFC 822`_) and not contain commas. The ``email`` value MUST be a
+in :rfc:`822`) and not contain commas. The ``email`` value MUST be a
 valid email address. Both keys are optional.
 
 Using the data to fill in :ref:`core metadata <core-metadata>` is as
@@ -303,5 +303,4 @@ provided via tooling later on.
   value, is acceptable).
 
 
-.. _RFC 822: https://datatracker.ietf.org/doc/html/rfc822
 .. _TOML: https://toml.io

source/specifications/direct-url.rst

@@ -23,8 +23,7 @@ specifying a direct URL reference (including a VCS URL).
 This file MUST NOT be created when installing a distribution from an other
 type of requirement (i.e. name plus version specifier).
 
-This JSON file MUST be a dictionary, compliant with `RFC 8259
-<https://datatracker.ietf.org/doc/html/rfc8259>`_ and UTF-8 encoded.
+This JSON file MUST be a dictionary, compliant with :rfc:`8259` and UTF-8 encoded.
 
 If present, it MUST contain at least two fields. The first one is ``url``, with
 type ``string``. Depending on what ``url`` refers to, the second field MUST be
@@ -82,7 +81,7 @@ present as a dictionary with the following key:
   in editable mode, ``false`` otherwise. If absent, default to ``false``.
 
 When ``url`` refers to a local directory, it MUST have the ``file`` sheme and
-be compliant with `RFC 8089 <https://datatracker.ietf.org/doc/html/rfc8089>`_. In
+be compliant with :rfc:`8089`. In
 particular, the path component must be absolute. Symbolic links SHOULD be
 preserved when making relative paths absolute.