Revert "docs: adjust syntax used for extlinks to include a blank <> with each use"

This reverts commit 94fecbd.

Author: 56kyle

docs/conf.py

@@ -57,60 +57,60 @@
 ]
 
 extlinks = {
-    "argocd": ("https://argo-cd.readthedocs.io/%s", None),
-    "autopep8": ("https://pypi.org/project/autopep8/%s", None),
-    "bandit-bandit": ("https://bandit.readthedocs.io/%s", None),
-    "bandit": ("https://github.com/PyCQA/bandit/%s", None),
-    "beartype": ("https://beartype.readthedocs.io/%s", None),
-    "bitbucket-pipelines": ("https://support.atlassian.com/bitbucket-cloud/docs/get-started-with-bitbucket-pipelines/%s", None),
-    "black": ("https://black.readthedocs.io/%s", None),
-    "build": ("https://pypa-build.readthedocs.io/%s", None),
-    "commitizen": ("https://commitizen-tools.github.io/commitizen/%s", None),
-    "coveragepy-coverage": ("https://coverage.readthedocs.io/%s", None),
-    "coveragepy": ("https://github.com/nedbat/coveragepy/%s", None),
-    "cruft": ("https://cruft.github.io/cruft/%s", None),
-    "docker-compose": ("https://docs.docker.com/compose/%s", None),
-    "docker": ("https://docs.docker.com/%s", None),
-    "flake8": ("https://flake8.pycqa.org/%s", None),
-    "flit": ("https://flit.pypa.io/%s", None),
-    "github-actions": ("https://docs.github.com/en/actions/%s", None),
-    "gitlab-ci": ("https://docs.gitlab.com/ee/ci/%s", None),
-    "hatch": ("https://hatch.pypa.io/%s", None),
-    "hatchling": ("https://hatch.pypa.io/latest/hatchling/%s", None),
-    "helm": ("https://helm.sh/%s", None),
-    "invoke": ("https://www.pyinvoke.org/%s", None),
-    "isort": ("https://pycqa.github.io/isort/%s", None),
-    "just": ("https://just.systems/%s", None),
-    "maturin": ("https://maturin.rs/%s", None),
-    "mkdocs": ("https://www.mkdocs.org/%s", None),
-    "mypy": ("https://mypy-lang.org/%s", None),
-    "myst-parser": ("https://myst-parser.readthedocs.io/%s", None),
-    "nox": ("https://nox.thea.codes/%s", None),
-    "pdm": ("https://pdm.fming.dev/%s", None),
-    "pip-audit": ("https://github.com/pypa/pip-audit/%s", None),
-    "pip": ("https://pip.pypa.io/%s", None),
-    "pip-tools": ("https://pip-tools.readthedocs.io/%s", None),
-    "podman": ("https://podman.io/%s", None),
-    "poethepoet": ("https://github.com/nat-n/poethepoet/%s", None),
-    "poetry": ("https://python-poetry.org/%s", None),
-    "pre-commit": ("https://pre-commit.com/%s", None),
-    "pydocstyle": ("https://www.pydocstyle.org/%s", None),
-    "pylint": ("https://pylint.pycqa.org/%s", None),
-    "pyright": ("https://github.com/microsoft/pyright/%s", None),
-    "pytest": ("https://docs.pytest.org/%s", None),
-    "pytest-pytest-cov": ("https://pytest-cov.readthedocs.io/%s", None),
-    "pytype": ("https://github.com/google/pytype/%s", None),
-    "ruff": ("https://docs.astral.sh/ruff/%s", None),
-    "safety": ("https://pyup.io/%s", None),
-    "setuptools": ("https://setuptools.pypa.io/%s", None),
-    "sonarcloud": ("https://sonarcloud.io/%s", None),
-    "sphinx": ("https://www.sphinx-doc.org/%s", None),
-    "sphinxautodoctypehints": ("https://sphinx-autodoc-typehints.readthedocs.io/%s", None),
-    "tox": ("https://tox.readthedocs.io/%s", None),
-    "twine": ("https://twine.readthedocs.io/%s", None),
-    "uv": ("https://docs.uv.dev/%s", None),
-    "virtualenv": ("https://virtualenv.pypa.io/%s", None),
-    "yapf": ("https://github.com/google/yapf/%s", None)
+    "argocd": ("https://argo-cd.readthedocs.io", None),
+    "autopep8": ("https://pypi.org/project/autopep8", None),
+    "bandit-bandit": ("https://bandit.readthedocs.io", None),
+    "bandit": ("https://github.com/PyCQA/bandit", None),
+    "beartype": ("https://beartype.readthedocs.io", None),
+    "bitbucket-pipelines": ("https://support.atlassian.com/bitbucket-cloud/docs/get-started-with-bitbucket-pipelines", None),
+    "black": ("https://black.readthedocs.io", None),
+    "build": ("https://pypa-build.readthedocs.io", None),
+    "commitizen": ("https://commitizen-tools.github.io/commitizen", None),
+    "coveragepy-coverage": ("https://coverage.readthedocs.io", None),
+    "coveragepy": ("https://github.com/nedbat/coveragepy", None),
+    "cruft": ("https://cruft.github.io/cruft", None),
+    "docker-compose": ("https://docs.docker.com/compose", None),
+    "docker": ("https://docs.docker.com", None),
+    "flake8": ("https://flake8.pycqa.org", None),
+    "flit": ("https://flit.pypa.io", None),
+    "github-actions": ("https://docs.github.com/en/actions", None),
+    "gitlab-ci": ("https://docs.gitlab.com/ee/ci", None),
+    "hatch": ("https://hatch.pypa.io", None),
+    "hatchling": ("https://hatch.pypa.io/latest/hatchling", None),
+    "helm": ("https://helm.sh", None),
+    "invoke": ("https://www.pyinvoke.org", None),
+    "isort": ("https://pycqa.github.io/isort", None),
+    "just": ("https://just.systems", None),
+    "maturin": ("https://maturin.rs", None),
+    "mkdocs": ("https://www.mkdocs.org", None),
+    "mypy": ("https://mypy-lang.org", None),
+    "myst-parser": ("https://myst-parser.readthedocs.io", None),
+    "nox": ("https://nox.thea.codes", None),
+    "pdm": ("https://pdm.fming.dev", None),
+    "pip-audit": ("https://github.com/pypa/pip-audit", None),
+    "pip": ("https://pip.pypa.io", None),
+    "pip-tools": ("https://pip-tools.readthedocs.io", None),
+    "podman": ("https://podman.io", None),
+    "poethepoet": ("https://github.com/nat-n/poethepoet", None),
+    "poetry": ("https://python-poetry.org", None),
+    "pre-commit": ("https://pre-commit.com", None),
+    "pydocstyle": ("https://www.pydocstyle.org", None),
+    "pylint": ("https://pylint.pycqa.org", None),
+    "pyright": ("https://github.com/microsoft/pyright", None),
+    "pytest": ("https://docs.pytest.org", None),
+    "pytest-pytest-cov": ("https://pytest-cov.readthedocs.io", None),
+    "pytype": ("https://github.com/google/pytype", None),
+    "ruff": ("https://docs.astral.sh/ruff", None),
+    "safety": ("https://pyup.io", None),
+    "setuptools": ("https://setuptools.pypa.io", None),
+    "sonarcloud": ("https://sonarcloud.io", None),
+    "sphinx": ("https://www.sphinx-doc.org", None),
+    "sphinxautodoctypehints": ("https://sphinx-autodoc-typehints.readthedocs.io", None),
+    "tox": ("https://tox.readthedocs.io", None),
+    "twine": ("https://twine.readthedocs.io", None),
+    "uv": ("https://docs.uv.dev", None),
+    "virtualenv": ("https://virtualenv.pypa.io", None),
+    "yapf": ("https://github.com/google/yapf", None)
 }
 
 intersphinx_mapping = {

docs/index.md

@@ -57,7 +57,7 @@ topics/18_pre-commit-hooks
 
 **Note:** The documentation you are reading _is for the template itself_. A project generated by this template will have its _own_ separate `docs/` directory for its project-specific documentation (API reference, tutorials, etc.).
 
-The generated project's documentation also uses {sphinx}`Sphinx<>` with MyST Markdown and integrates API documentation via `autodoc`. You can build your project's documentation by navigating into the generated project directory and running:
+The generated project's documentation also uses {sphinx}`Sphinx` with MyST Markdown and integrates API documentation via `autodoc`. You can build your project's documentation by navigating into the generated project directory and running:
 
 ```bash
 uvx nox -s docs

docs/maintenance.md

@@ -8,7 +8,7 @@ Maintaining a project template is an ongoing effort that involves updating depen
 
 ## Template Dependencies and Development Environment
 
-The `cookiecutter-robust-python` template repository is itself a project with dependencies needed for its development and maintenance. These include `cookiecutter`, the specific versions of the tools evaluated (to ensure compatibility and test against them), and maintenance-specific tools (like {commitizen}`Commitizen<>` for template versioning, {nox}`Nox<>` for template task automation, potentially testing frameworks for the template's functionality).
+The `cookiecutter-robust-python` template repository is itself a project with dependencies needed for its development and maintenance. These include `cookiecutter`, the specific versions of the tools evaluated (to ensure compatibility and test against them), and maintenance-specific tools (like {commitizen}`Commitizen` for template versioning, {nox}`Nox` for template task automation, potentially testing frameworks for the template's functionality).
 
 The template's `pyproject.toml` file at the **template repository root** lists these dependencies.
 
@@ -48,20 +48,20 @@ The template repository uses its own `noxfile.py` at the **template repository r
 
 ## Keeping Template Tooling and Dependencies Current
 
-As the tools recommended by the template ({uv}`uv<>`, {ruff}`Ruff<>`, {pyright}`Pyright<>`, {pytest-pytest-cov}`pytest<>`, etc.) release new versions, you will need to:
+As the tools recommended by the template ({uv}`uv`, {ruff}`Ruff`, {pyright}`Pyright`, {pytest-pytest-cov}`pytest`, etc.) release new versions, you will need to:
 
 1.  **Update Template Dependencies:** Manually update the version specifiers for the desired tools in the template's **`pyproject.toml` at the template root**. Run `uv sync` at the template root to update the template's own `uv.lock` file with the new versions.
 2.  **Update Template Configuration:** Review release notes for the updated tools. Modify the **separate configuration files** (like `.ruff.toml`, `pyrightconfig.json`, `.coveragerc`) and `pyproject.toml` (e.g., `[tool.uv]`, `[tool.pytest]`) within the **template structure** (e.g., `{{cookiecutter.project_slug}}/pyproject.toml`, `{{cookiecutter.project_slug}}/.ruff.toml`) if the tools have breaking changes in configuration or recommended settings.
 3.  **Test Template:** Run the template's own checks and tests (`uvx nox`) to ensure the template still functions correctly and generates projects with working workflows using the new tool versions. This is crucial! Consider adding tests that render a project and run its default checks/tests within the template's own CI.
-4.  **Update Pre-commit Hook `rev`s:** For tools used as {pre-commit}`pre-commit<>` hooks, update the `rev` (version hash/tag) for those hooks in the template's **`.pre-commit-config.yaml` at the template root** to match tested, compatible versions of the hook repositories. You can use `uvx nox -s pre-commit -- autoupdate` in the template repository to update these `rev`s interactively.
+4.  **Update Pre-commit Hook `rev`s:** For tools used as {pre-commit}`pre-commit` hooks, update the `rev` (version hash/tag) for those hooks in the template's **`.pre-commit-config.yaml` at the template root** to match tested, compatible versions of the hook repositories. You can use `uvx nox -s pre-commit -- autoupdate` in the template repository to update these `rev`s interactively.
 5.  **Update CI/CD Example Configs:** Ensure the versions referenced in example CI/CD workflow files (`.github/workflows/`, `bitbucket-pipelines.yml`, etc.) are current and consistent with the tested tool versions (e.g., Python versions tested against, commands to install uv/Nox if pinned).
 6.  **Update Documentation:** **CRITICAL.** If tool updates change behavior, configuration, workflow steps, or even render previous justifications less valid, **update the documentation** (specifically the `docs/topics/` files) to reflect the current state and rationale. This ensures the documentation remains accurate and the justifications for tool choices are based on the _current_ versions and understanding.
 
 ## Keeping Generated Projects Updated
 
-A project generated from this template is a copy at a point in time. Template updates do **not** automatically apply to existing generated projects. We recommend using **{cruft}`cruft<>`** to help manage updates in projects _after_ they've been generated:
+A project generated from this template is a copy at a point in time. Template updates do **not** automatically apply to existing generated projects. We recommend using **{cruft}`cruft`** to help manage updates in projects _after_ they've been generated:
 
-1.  **Ensure `cruft` is Used:** During template generation, the `{{cookiecutter.project_slug}}` should have a <>`.cruft.json` file created (handled automatically by {cruft}`cruft<>` if the template is run via `cruft create`, or added as a post-gen hook). This file tracks the template version used.
+1.  **Ensure `cruft` is Used:** During template generation, the `{{cookiecutter.project_slug}}` should have a `.cruft.json` file created (handled automatically by {cruft}`cruft` if the template is run via `cruft create`, or added as a post-gen hook). This file tracks the template version used.
 2.  **Instruct Users on `cruft`:** The documentation _within the generated project's_ `docs/` (e.g., the Getting Started guide) should clearly explain how to use `cruft` (`cruft check`, `cruft update`) to bring in changes from template updates. You can mention running `uvx nox -s cruft-check` (if you add a Nox session for this) or integrating `cruft check --exit-code` into the generated project's CI workflow to alert users of template updates.
 
 ## Releasing a New Template Version
@@ -70,7 +70,7 @@ Releasing a new version of the template itself follows a standard process, often
 
 1.  **Finalize Changes:** Ensure all desired updates for the release are committed to the main branch of the template repository.
 2.  **Verify Template Health:** Run the full suite of checks and tests for the template itself (`uvx nox`) to confirm it's functioning correctly.
-3.  **Run Commitizen Bump:** Use {commitizen}`Commitizen<>` (installed as a dev dependency in the template repo) to automatically bump the calendar version string(s) in your template files (e.g., `docs/conf.py`), create a Git tag (e.g., `2025.04.28`), and generate/update a `CHANGELOG.md` for the template repository.
+3.  **Run Commitizen Bump:** Use {commitizen}`Commitizen` (installed as a dev dependency in the template repo) to automatically bump the calendar version string(s) in your template files (e.g., `docs/conf.py`), create a Git tag (e.g., `2025.04.28`), and generate/update a `CHANGELOG.md` for the template repository.
     ```bash
     uvx cz bump # Run in template repo root; follow prompts. Updates version, tags, changelog.
     ```
@@ -83,4 +83,4 @@ Releasing a new version of the template itself follows a standard process, often
 
 ## Documenting Template Changes
 
-Maintain a `CHANGELOG.md` file at the **template repository root** to clearly document the changes included in each template release (often generated automatically by {commitizen}`Commitizen<>`). This helps users understand the benefits and potential impacts of updating their generated projects to a newer template version. Link to specific documentation topics if updates involve significant changes in tooling or workflows.
+Maintain a `CHANGELOG.md` file at the **template repository root** to clearly document the changes included in each template release (often generated automatically by {commitizen}`Commitizen`). This helps users understand the benefits and potential impacts of updating their generated projects to a newer template version. Link to specific documentation topics if updates involve significant changes in tooling or workflows.