Update instance repo from cookiecutter template

Author: github-actions[bot]

.cruft.json

@@ -1,6 +1,6 @@
 {
   "template": "/home/runner/work/cookiecutter-scverse/cookiecutter-scverse",
-  "commit": "af5404e37dd5144a952d2262665d5b78192d1da7",
+  "commit": "c9d52d04e146e655f203624ab4f46df868ec5752",
   "checkout": null,
   "context": {
     "cookiecutter": {
@@ -36,7 +36,7 @@
         "trim_blocks": true
       },
       "_template": "/home/runner/work/cookiecutter-scverse/cookiecutter-scverse",
-      "_commit": "af5404e37dd5144a952d2262665d5b78192d1da7"
+      "_commit": "c9d52d04e146e655f203624ab4f46df868ec5752"
     }
   },
   "directory": null

docs/conf.py

@@ -59,7 +59,7 @@
     "sphinxcontrib.bibtex",
     "sphinxcontrib.katex",
     "sphinx_autodoc_typehints",
-    "sphinx_tabs.tabs",
+    "sphinx_design",
     "IPython.sphinxext.ipython_console_highlighting",
     "sphinxext.opengraph",
     *[p.stem for p in (HERE / "extensions").glob("*.py")],

docs/contributing.md

@@ -33,8 +33,9 @@ it is still possible to use different tools to manage dependencies, such as `uv`
 In addition to the packages needed to _use_ this package,
 you need additional python packages to [run tests](#writing-tests) and [build the documentation](#docs-building).
 
-:::::{tabs}
-::::{group-tab} Hatch
+:::::{tab-set}
+::::{tab-item} Hatch
+:sync: hatch
 
 On the command line, you typically interact with hatch through its command line interface (CLI).
 Running one of the following commands will automatically resolve the environments for testing and
@@ -94,7 +95,8 @@ In this future, this may become easier through a hatch vscode extension.
 
 ::::
 
-::::{group-tab} uv
+::::{tab-item} uv
+:sync: uv
 
 A popular choice for managing virtual environments is [uv][].
 The main disadvantage compared to hatch is that it supports only a single environment per project at a time,
@@ -113,7 +115,8 @@ The `.venv` directory is typically automatically discovered by IDEs such as VS C
 
 ::::
 
-::::{group-tab} Pip
+::::{tab-item} Pip
+:sync: pip
 
 Pip is nowadays mostly superseded by environment manager such as [hatch][].
 However, for the sake of completeness, and since it’s ubiquitously available,
@@ -185,8 +188,9 @@ hatch env find hatch-test  # list all possible test environment paths
 
 Alternatively, you can run all tests from the command line by executing
 
-:::::{tabs}
-::::{group-tab} Hatch
+:::::{tab-set}
+::::{tab-item} Hatch
+:sync: hatch
 
 ```bash
 hatch test  # test with the highest supported Python version
@@ -196,15 +200,17 @@ hatch test --all  # test with all supported Python versions
 
 ::::
 
-::::{group-tab} uv
+::::{tab-item} uv
+:sync: uv
 
 ```bash
 uv run pytest
 ```
 
 ::::
 
-::::{group-tab} Pip
+::::{tab-item} Pip
+:sync: pip
 
 ```bash
 source .venv/bin/activate
@@ -298,8 +304,9 @@ please check out [this feature request][issue-render-notebooks] in the `cookiecu
 
 ### Building the docs locally
 
-:::::{tabs}
-::::{group-tab} Hatch
+:::::{tab-set}
+::::{tab-item} Hatch
+:sync: hatch
 
 ```bash
 hatch run docs:build
@@ -308,7 +315,8 @@ hatch run docs:open
 
 ::::
 
-::::{group-tab} uv
+::::{tab-item} uv
+:sync: uv
 
 ```bash
 cd docs
@@ -318,7 +326,8 @@ uv run sphinx-build -M html . _build -W
 
 ::::
 
-::::{group-tab} Pip
+::::{tab-item} Pip
+:sync: pip
 
 ```bash
 source .venv/bin/activate

pyproject.toml

@@ -51,7 +51,7 @@ doc = [
   "sphinx-autodoc-typehints",
   "sphinx-book-theme>=1",
   "sphinx-copybutton",
-  "sphinx-tabs",
+  "sphinx-design",
   "sphinxcontrib-bibtex>=1",
   "sphinxcontrib-katex",
   "sphinxext-opengraph",