diff --git a/.github/workflows/build_and_deploy.yml b/.github/workflows/build_and_deploy.yml
index 0059c025b..7477861cc 100644
--- a/.github/workflows/build_and_deploy.yml
+++ b/.github/workflows/build_and_deploy.yml
@@ -17,6 +17,11 @@ on:
     branches:
       - main
   workflow_dispatch:
+    inputs:
+      target_directory:
+        description: 'The directory to deploy the docs to'
+        required: true
+        default: 'dev'
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
@@ -104,23 +109,6 @@ jobs:
           # Downloads to '/home/runner/work/docs/docs/html'
           path: html
 
-      - name: get directory name
-        # if this is a tag, use the tag name as the directory name else dev
-        env:
-          REF: ${{ github.ref }}
-        run: |
-          TAG="${GITHUB_REF/refs\/tags\/v/}"
-          VER="${TAG/a*/}"  # remove alpha identifier
-          VER="${VER/b*/}"  # remove beta identifier
-          VER="${VER/rc*/}"  # remove rc identifier
-          VER="${VER/post*/}"  # remove post identifier
-
-          if [[ "$REF" == "refs/tags/v"* ]]; then
-            echo "branch_name=$VER" >> "$GITHUB_ENV"
-          else
-            echo "branch_name=dev" >> "$GITHUB_ENV"
-          fi
-
       - name: Deploy Docs
         if: (github.event_name == 'push' || github.event_name == 'workflow_dispatch') && (startsWith(github.ref, 'refs/tags/v') || startsWith(github.ref, 'refs/heads/main'))
         uses: peaceiris/actions-gh-pages@v4
@@ -129,5 +117,5 @@ jobs:
           external_repository: napari/napari.github.io
           publish_dir: ./html
           publish_branch: gh-pages
-          destination_dir: ${{ env.branch_name }}
+          destination_dir: ${{ github.event.inputs.target_directory || 'dev' }}
           cname: napari.org
diff --git a/EULA.md b/EULA.md
index 378366f75..5bc9b2d74 100644
--- a/EULA.md
+++ b/EULA.md
@@ -7,7 +7,7 @@ https://napari.org.
 
 <!-- Links -->
 
-[napari_installers]: https://napari.org/stable/index.html#installation
+[napari_installers]: https://napari.org/stable/tutorials/fundamentals/installation.html
 
 <!-- List of EULAs starts here -->
 <!--
diff --git a/docs/_scripts/update_preference_docs.py b/docs/_scripts/update_preference_docs.py
index 086302320..ef60c7fef 100644
--- a/docs/_scripts/update_preference_docs.py
+++ b/docs/_scripts/update_preference_docs.py
@@ -6,7 +6,7 @@
 from qtpy.QtWidgets import QMessageBox
 
 from napari._qt.dialogs.preferences_dialog import PreferencesDialog
-from napari._qt.qt_event_loop import get_app
+from napari._qt.qt_event_loop import get_qapp
 from napari._qt.qt_resources import get_stylesheet
 from napari.settings import NapariSettings
 
@@ -99,7 +99,7 @@ def generate_images():
     section of the docs.
     """
 
-    app = get_app()
+    app = get_qapp()
     pref = PreferencesDialog()
     pref.setStyleSheet(get_stylesheet("dark"))
     pref.show()
diff --git a/docs/images/2D-button.png b/docs/_static/images/2D-button.png
similarity index 100%
rename from docs/images/2D-button.png
rename to docs/_static/images/2D-button.png
diff --git a/docs/tutorials/assets/tutorials/3D_button.png b/docs/_static/images/3D-button.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/3D_button.png
rename to docs/_static/images/3D-button.png
diff --git a/docs/images/3D_paths.png b/docs/_static/images/3D_paths.png
similarity index 100%
rename from docs/images/3D_paths.png
rename to docs/_static/images/3D_paths.png
diff --git a/docs/guides/images/3d_interaction.ai b/docs/_static/images/3d_interaction.ai
similarity index 100%
rename from docs/guides/images/3d_interaction.ai
rename to docs/_static/images/3d_interaction.ai
diff --git a/docs/guides/images/3d_interaction_click_line.png b/docs/_static/images/3d_interaction_click_line.png
similarity index 100%
rename from docs/guides/images/3d_interaction_click_line.png
rename to docs/_static/images/3d_interaction_click_line.png
diff --git a/docs/guides/images/3d_interaction_coordianates.png b/docs/_static/images/3d_interaction_coordianates.png
similarity index 100%
rename from docs/guides/images/3d_interaction_coordianates.png
rename to docs/_static/images/3d_interaction_coordianates.png
diff --git a/docs/guides/images/3d_interaction_ray_intersection.png b/docs/_static/images/3d_interaction_ray_intersection.png
similarity index 100%
rename from docs/guides/images/3d_interaction_ray_intersection.png
rename to docs/_static/images/3d_interaction_ray_intersection.png
diff --git a/docs/images/IPython.png b/docs/_static/images/IPython.png
similarity index 100%
rename from docs/images/IPython.png
rename to docs/_static/images/IPython.png
diff --git a/docs/tutorials/assets/tutorials/Viewer-with-arrows.png b/docs/_static/images/Viewer-with-arrows.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/Viewer-with-arrows.png
rename to docs/_static/images/Viewer-with-arrows.png
diff --git a/docs/tutorials/assets/tutorials/add_points.png b/docs/_static/images/add_points.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/add_points.png
rename to docs/_static/images/add_points.png
diff --git a/docs/images/add_vectors_image.png b/docs/_static/images/add_vectors_image.png
similarity index 100%
rename from docs/images/add_vectors_image.png
rename to docs/_static/images/add_vectors_image.png
diff --git a/docs/tutorials/assets/tutorials/annotated_bbox.png b/docs/_static/images/annotated_bbox.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/annotated_bbox.png
rename to docs/_static/images/annotated_bbox.png
diff --git a/docs/guides/images/blending.png b/docs/_static/images/blending.png
similarity index 100%
rename from docs/guides/images/blending.png
rename to docs/_static/images/blending.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_02.png b/docs/_static/images/bundle_02.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_02.png
rename to docs/_static/images/bundle_02.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_04.png b/docs/_static/images/bundle_04.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_04.png
rename to docs/_static/images/bundle_04.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_06.png b/docs/_static/images/bundle_06.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_06.png
rename to docs/_static/images/bundle_06.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_07.png b/docs/_static/images/bundle_07.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_07.png
rename to docs/_static/images/bundle_07.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_09.png b/docs/_static/images/bundle_09.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_09.png
rename to docs/_static/images/bundle_09.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_10.png b/docs/_static/images/bundle_10.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_10.png
rename to docs/_static/images/bundle_10.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_11.png b/docs/_static/images/bundle_11.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_11.png
rename to docs/_static/images/bundle_11.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_13.png b/docs/_static/images/bundle_13.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_13.png
rename to docs/_static/images/bundle_13.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_17.png b/docs/_static/images/bundle_17.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_17.png
rename to docs/_static/images/bundle_17.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_18.png b/docs/_static/images/bundle_18.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_18.png
rename to docs/_static/images/bundle_18.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_19.png b/docs/_static/images/bundle_19.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_19.png
rename to docs/_static/images/bundle_19.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_20.png b/docs/_static/images/bundle_20.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_20.png
rename to docs/_static/images/bundle_20.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_21.png b/docs/_static/images/bundle_21.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_21.png
rename to docs/_static/images/bundle_21.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_22.png b/docs/_static/images/bundle_22.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_22.png
rename to docs/_static/images/bundle_22.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_24.png b/docs/_static/images/bundle_24.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_24.png
rename to docs/_static/images/bundle_24.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_28.png b/docs/_static/images/bundle_28.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_28.png
rename to docs/_static/images/bundle_28.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_29.png b/docs/_static/images/bundle_29.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_29.png
rename to docs/_static/images/bundle_29.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_30.png b/docs/_static/images/bundle_30.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_30.png
rename to docs/_static/images/bundle_30.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_31.png b/docs/_static/images/bundle_31.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_31.png
rename to docs/_static/images/bundle_31.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_32.png b/docs/_static/images/bundle_32.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_32.png
rename to docs/_static/images/bundle_32.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_33.png b/docs/_static/images/bundle_33.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_33.png
rename to docs/_static/images/bundle_33.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_34.png b/docs/_static/images/bundle_34.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_34.png
rename to docs/_static/images/bundle_34.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_35.png b/docs/_static/images/bundle_35.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_35.png
rename to docs/_static/images/bundle_35.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_dev_warning.png b/docs/_static/images/bundle_dev_warning.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_dev_warning.png
rename to docs/_static/images/bundle_dev_warning.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_open.png b/docs/_static/images/bundle_open.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_open.png
rename to docs/_static/images/bundle_open.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_open_anyway.png b/docs/_static/images/bundle_open_anyway.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_open_anyway.png
rename to docs/_static/images/bundle_open_anyway.png
diff --git a/docs/tutorials/assets/tutorials/installation/bundle_security_privacy.png b/docs/_static/images/bundle_security_privacy.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/bundle_security_privacy.png
rename to docs/_static/images/bundle_security_privacy.png
diff --git a/docs/guides/images/chunked-format.png b/docs/_static/images/chunked-format.png
similarity index 100%
rename from docs/guides/images/chunked-format.png
rename to docs/_static/images/chunked-format.png
diff --git a/docs/developers/contributing/documentation/images/circleci-link.png b/docs/_static/images/circleci-link.png
similarity index 100%
rename from docs/developers/contributing/documentation/images/circleci-link.png
rename to docs/_static/images/circleci-link.png
diff --git a/docs/tutorials/assets/tutorials/console.png b/docs/_static/images/console.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/console.png
rename to docs/_static/images/console.png
diff --git a/docs/guides/images/context_type_hint.png b/docs/_static/images/context_type_hint.png
similarity index 100%
rename from docs/guides/images/context_type_hint.png
rename to docs/_static/images/context_type_hint.png
diff --git a/docs/images/coverage_report.png b/docs/_static/images/coverage_report.png
similarity index 100%
rename from docs/images/coverage_report.png
rename to docs/_static/images/coverage_report.png
diff --git a/docs/tutorials/assets/tutorials/dask_repr.png b/docs/_static/images/dask_repr.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/dask_repr.png
rename to docs/_static/images/dask_repr.png
diff --git a/docs/tutorials/assets/tutorials/dims_roll_lock_widget.png b/docs/_static/images/dims_roll_lock_widget.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/dims_roll_lock_widget.png
rename to docs/_static/images/dims_roll_lock_widget.png
diff --git a/docs/developers/contributing/documentation/images/doc-ci-1.png b/docs/_static/images/doc-ci-1.png
similarity index 100%
rename from docs/developers/contributing/documentation/images/doc-ci-1.png
rename to docs/_static/images/doc-ci-1.png
diff --git a/docs/developers/contributing/documentation/images/doc-ci-2.png b/docs/_static/images/doc-ci-2.png
similarity index 100%
rename from docs/developers/contributing/documentation/images/doc-ci-2.png
rename to docs/_static/images/doc-ci-2.png
diff --git a/docs/developers/contributing/documentation/images/doc-ci-3.png b/docs/_static/images/doc-ci-3.png
similarity index 100%
rename from docs/developers/contributing/documentation/images/doc-ci-3.png
rename to docs/_static/images/doc-ci-3.png
diff --git a/docs/images/edit_token_permissions.png b/docs/_static/images/edit_token_permissions.png
similarity index 100%
rename from docs/images/edit_token_permissions.png
rename to docs/_static/images/edit_token_permissions.png
diff --git a/docs/guides/images/example-1320.png b/docs/_static/images/example-1320.png
similarity index 100%
rename from docs/guides/images/example-1320.png
rename to docs/_static/images/example-1320.png
diff --git a/docs/images/fine_grained_token.png b/docs/_static/images/fine_grained_token.png
similarity index 100%
rename from docs/images/fine_grained_token.png
rename to docs/_static/images/fine_grained_token.png
diff --git a/docs/images/labels-layer-eraser.png b/docs/_static/images/labels-layer-eraser.png
similarity index 100%
rename from docs/images/labels-layer-eraser.png
rename to docs/_static/images/labels-layer-eraser.png
diff --git a/docs/tutorials/assets/tutorials/launch_cli_empty.png b/docs/_static/images/launch_cli_empty.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/launch_cli_empty.png
rename to docs/_static/images/launch_cli_empty.png
diff --git a/docs/tutorials/assets/tutorials/launch_cli_image.png b/docs/_static/images/launch_cli_image.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/launch_cli_image.png
rename to docs/_static/images/launch_cli_image.png
diff --git a/docs/tutorials/assets/tutorials/launch_ipython.png b/docs/_static/images/launch_ipython.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/launch_ipython.png
rename to docs/_static/images/launch_ipython.png
diff --git a/docs/tutorials/assets/tutorials/launch_jupyter.png b/docs/_static/images/launch_jupyter.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/launch_jupyter.png
rename to docs/_static/images/launch_jupyter.png
diff --git a/docs/tutorials/assets/tutorials/launch_script.png b/docs/_static/images/launch_script.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/launch_script.png
rename to docs/_static/images/launch_script.png
diff --git a/docs/tutorials/assets/tutorials/layerlist.png b/docs/_static/images/layerlist.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/layerlist.png
rename to docs/_static/images/layerlist.png
diff --git a/docs/images/lines_not_run_highlighted_in_red.png b/docs/_static/images/lines_not_run_highlighted_in_red.png
similarity index 100%
rename from docs/images/lines_not_run_highlighted_in_red.png
rename to docs/_static/images/lines_not_run_highlighted_in_red.png
diff --git a/docs/images/logo.png b/docs/_static/images/logo.png
similarity index 100%
rename from docs/images/logo.png
rename to docs/_static/images/logo.png
diff --git a/docs/tutorials/assets/tutorials/main-menu-file-sub-menu-preferences.png b/docs/_static/images/main-menu-file-sub-menu-preferences.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/main-menu-file-sub-menu-preferences.png
rename to docs/_static/images/main-menu-file-sub-menu-preferences.png
diff --git a/docs/tutorials/assets/tutorials/main-menu-file.png b/docs/_static/images/main-menu-file.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/main-menu-file.png
rename to docs/_static/images/main-menu-file.png
diff --git a/docs/tutorials/assets/tutorials/main-menu-help.png b/docs/_static/images/main-menu-help.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/main-menu-help.png
rename to docs/_static/images/main-menu-help.png
diff --git a/docs/tutorials/assets/tutorials/main-menu-plugins.png b/docs/_static/images/main-menu-plugins.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/main-menu-plugins.png
rename to docs/_static/images/main-menu-plugins.png
diff --git a/docs/tutorials/assets/tutorials/main-menu-view.png b/docs/_static/images/main-menu-view.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/main-menu-view.png
rename to docs/_static/images/main-menu-view.png
diff --git a/docs/tutorials/assets/tutorials/main-menu-window.png b/docs/_static/images/main-menu-window.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/main-menu-window.png
rename to docs/_static/images/main-menu-window.png
diff --git a/docs/tutorials/assets/tutorials/nD_labels.png b/docs/_static/images/nD_labels.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/nD_labels.png
rename to docs/_static/images/nD_labels.png
diff --git a/docs/images/napari-logo-3-with-guides.png b/docs/_static/images/napari-logo-3-with-guides.png
similarity index 100%
rename from docs/images/napari-logo-3-with-guides.png
rename to docs/_static/images/napari-logo-3-with-guides.png
diff --git a/docs/images/napari-logo-3.png b/docs/_static/images/napari-logo-3.png
similarity index 100%
rename from docs/images/napari-logo-3.png
rename to docs/_static/images/napari-logo-3.png
diff --git a/docs/images/napari-logo-old-new.png b/docs/_static/images/napari-logo-old-new.png
similarity index 100%
rename from docs/images/napari-logo-old-new.png
rename to docs/_static/images/napari-logo-old-new.png
diff --git a/docs/images/napari_plugins_1st_napari_get_reader.png b/docs/_static/images/napari_plugins_1st_napari_get_reader.png
similarity index 100%
rename from docs/images/napari_plugins_1st_napari_get_reader.png
rename to docs/_static/images/napari_plugins_1st_napari_get_reader.png
diff --git a/docs/images/napari_plugins_2nd_reader_function.png b/docs/_static/images/napari_plugins_2nd_reader_function.png
similarity index 100%
rename from docs/images/napari_plugins_2nd_reader_function.png
rename to docs/_static/images/napari_plugins_2nd_reader_function.png
diff --git a/docs/images/napari_plugins_3rd_pytest_passed.png b/docs/_static/images/napari_plugins_3rd_pytest_passed.png
similarity index 100%
rename from docs/images/napari_plugins_3rd_pytest_passed.png
rename to docs/_static/images/napari_plugins_3rd_pytest_passed.png
diff --git a/docs/images/napari_plugins_4th_test_get_reader_returns_callable-failed.png b/docs/_static/images/napari_plugins_4th_test_get_reader_returns_callable-failed.png
similarity index 100%
rename from docs/images/napari_plugins_4th_test_get_reader_returns_callable-failed.png
rename to docs/_static/images/napari_plugins_4th_test_get_reader_returns_callable-failed.png
diff --git a/docs/images/napari_plugins_5th_tests_passed.png b/docs/_static/images/napari_plugins_5th_tests_passed.png
similarity index 100%
rename from docs/images/napari_plugins_5th_tests_passed.png
rename to docs/_static/images/napari_plugins_5th_tests_passed.png
diff --git a/docs/images/ndisplay.png b/docs/_static/images/ndisplay.png
similarity index 100%
rename from docs/images/ndisplay.png
rename to docs/_static/images/ndisplay.png
diff --git a/docs/guides/images/octree.png b/docs/_static/images/octree.png
similarity index 100%
rename from docs/guides/images/octree.png
rename to docs/_static/images/octree.png
diff --git a/docs/guides/images/paging-chunks.png b/docs/_static/images/paging-chunks.png
similarity index 100%
rename from docs/guides/images/paging-chunks.png
rename to docs/_static/images/paging-chunks.png
diff --git a/docs/images/pan-zoom-tool.png b/docs/_static/images/pan-zoom-tool.png
similarity index 100%
rename from docs/images/pan-zoom-tool.png
rename to docs/_static/images/pan-zoom-tool.png
diff --git a/docs/images/plugin-install-dialog.png b/docs/_static/images/plugin-install-dialog.png
similarity index 100%
rename from docs/images/plugin-install-dialog.png
rename to docs/_static/images/plugin-install-dialog.png
diff --git a/docs/images/plugin-menu.png b/docs/_static/images/plugin-menu.png
similarity index 100%
rename from docs/images/plugin-menu.png
rename to docs/_static/images/plugin-menu.png
diff --git a/docs/images/point-adding-tool.png b/docs/_static/images/point-adding-tool.png
similarity index 100%
rename from docs/images/point-adding-tool.png
rename to docs/_static/images/point-adding-tool.png
diff --git a/docs/images/point-deleting-tool.png b/docs/_static/images/point-deleting-tool.png
similarity index 100%
rename from docs/images/point-deleting-tool.png
rename to docs/_static/images/point-deleting-tool.png
diff --git a/docs/images/point-selecting-tool.png b/docs/_static/images/point-selecting-tool.png
similarity index 100%
rename from docs/images/point-selecting-tool.png
rename to docs/_static/images/point-selecting-tool.png
diff --git a/docs/tutorials/assets/tutorials/points_save_dialog.png b/docs/_static/images/points_save_dialog.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/points_save_dialog.png
rename to docs/_static/images/points_save_dialog.png
diff --git a/docs/guides/images/rendering.png b/docs/_static/images/rendering.png
similarity index 100%
rename from docs/guides/images/rendering.png
rename to docs/_static/images/rendering.png
diff --git a/docs/tutorials/assets/tutorials/rotated-image.png b/docs/_static/images/rotated-image.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/rotated-image.png
rename to docs/_static/images/rotated-image.png
diff --git a/docs/images/screenshot-add-image.png b/docs/_static/images/screenshot-add-image.png
similarity index 100%
rename from docs/images/screenshot-add-image.png
rename to docs/_static/images/screenshot-add-image.png
diff --git a/docs/images/second_coverage_report.png b/docs/_static/images/second_coverage_report.png
similarity index 100%
rename from docs/images/second_coverage_report.png
rename to docs/_static/images/second_coverage_report.png
diff --git a/docs/images/secrets_section.png b/docs/_static/images/secrets_section.png
similarity index 100%
rename from docs/images/secrets_section.png
rename to docs/_static/images/secrets_section.png
diff --git a/docs/tutorials/assets/tutorials/segmentation_bbox.png b/docs/_static/images/segmentation_bbox.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/segmentation_bbox.png
rename to docs/_static/images/segmentation_bbox.png
diff --git a/docs/tutorials/assets/tutorials/segmentation_labels.png b/docs/_static/images/segmentation_labels.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/segmentation_labels.png
rename to docs/_static/images/segmentation_labels.png
diff --git a/docs/images/shape-add-ellipses.png b/docs/_static/images/shape-add-ellipses.png
similarity index 100%
rename from docs/images/shape-add-ellipses.png
rename to docs/_static/images/shape-add-ellipses.png
diff --git a/docs/images/shape-add-lasso.png b/docs/_static/images/shape-add-lasso.png
similarity index 100%
rename from docs/images/shape-add-lasso.png
rename to docs/_static/images/shape-add-lasso.png
diff --git a/docs/images/shape-add-lines.png b/docs/_static/images/shape-add-lines.png
similarity index 100%
rename from docs/images/shape-add-lines.png
rename to docs/_static/images/shape-add-lines.png
diff --git a/docs/images/shape-add-path.png b/docs/_static/images/shape-add-path.png
similarity index 100%
rename from docs/images/shape-add-path.png
rename to docs/_static/images/shape-add-path.png
diff --git a/docs/images/shape-add-polygons.png b/docs/_static/images/shape-add-polygons.png
similarity index 100%
rename from docs/images/shape-add-polygons.png
rename to docs/_static/images/shape-add-polygons.png
diff --git a/docs/images/shape-add-rectangles.png b/docs/_static/images/shape-add-rectangles.png
similarity index 100%
rename from docs/images/shape-add-rectangles.png
rename to docs/_static/images/shape-add-rectangles.png
diff --git a/docs/images/shape-delete-shape.png b/docs/_static/images/shape-delete-shape.png
similarity index 100%
rename from docs/images/shape-delete-shape.png
rename to docs/_static/images/shape-delete-shape.png
diff --git a/docs/images/shape-move-to-back.png b/docs/_static/images/shape-move-to-back.png
similarity index 100%
rename from docs/images/shape-move-to-back.png
rename to docs/_static/images/shape-move-to-back.png
diff --git a/docs/images/shape-move-to-front.png b/docs/_static/images/shape-move-to-front.png
similarity index 100%
rename from docs/images/shape-move-to-front.png
rename to docs/_static/images/shape-move-to-front.png
diff --git a/docs/images/shape-select-shape.png b/docs/_static/images/shape-select-shape.png
similarity index 100%
rename from docs/images/shape-select-shape.png
rename to docs/_static/images/shape-select-shape.png
diff --git a/docs/images/shape-vertex-insert.png b/docs/_static/images/shape-vertex-insert.png
similarity index 100%
rename from docs/images/shape-vertex-insert.png
rename to docs/_static/images/shape-vertex-insert.png
diff --git a/docs/images/shape-vertices-select.png b/docs/_static/images/shape-vertices-select.png
similarity index 100%
rename from docs/images/shape-vertices-select.png
rename to docs/_static/images/shape-vertices-select.png
diff --git a/docs/images/shape_vertex_delete.png b/docs/_static/images/shape_vertex_delete.png
similarity index 100%
rename from docs/images/shape_vertex_delete.png
rename to docs/_static/images/shape_vertex_delete.png
diff --git a/docs/images/test_coverage_htmlcov_directory.png b/docs/_static/images/test_coverage_htmlcov_directory.png
similarity index 100%
rename from docs/images/test_coverage_htmlcov_directory.png
rename to docs/_static/images/test_coverage_htmlcov_directory.png
diff --git a/docs/images/tests.png b/docs/_static/images/tests.png
similarity index 100%
rename from docs/images/tests.png
rename to docs/_static/images/tests.png
diff --git a/docs/images/token_permission_form.png b/docs/_static/images/token_permission_form.png
similarity index 100%
rename from docs/images/token_permission_form.png
rename to docs/_static/images/token_permission_form.png
diff --git a/docs/images/token_permission_selection.png b/docs/_static/images/token_permission_selection.png
similarity index 100%
rename from docs/images/token_permission_selection.png
rename to docs/_static/images/token_permission_selection.png
diff --git a/docs/tutorials/assets/tutorials/tracks_btrack.png b/docs/_static/images/tracks_btrack.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/tracks_btrack.png
rename to docs/_static/images/tracks_btrack.png
diff --git a/docs/images/transform-icon.svg b/docs/_static/images/transform-icon.svg
similarity index 100%
rename from docs/images/transform-icon.svg
rename to docs/_static/images/transform-icon.svg
diff --git a/docs/images/transform-tool.png b/docs/_static/images/transform-tool.png
similarity index 100%
rename from docs/images/transform-tool.png
rename to docs/_static/images/transform-tool.png
diff --git a/docs/images/update_token_permissions.png b/docs/_static/images/update_token_permissions.png
similarity index 100%
rename from docs/images/update_token_permissions.png
rename to docs/_static/images/update_token_permissions.png
diff --git a/docs/tutorials/assets/tutorials/viewer-buttons.png b/docs/_static/images/viewer-buttons.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/viewer-buttons.png
rename to docs/_static/images/viewer-buttons.png
diff --git a/docs/tutorials/assets/tutorials/viewer_layout.jpg b/docs/_static/images/viewer_layout.jpg
similarity index 100%
rename from docs/tutorials/assets/tutorials/viewer_layout.jpg
rename to docs/_static/images/viewer_layout.jpg
diff --git a/docs/images/vs_code_debug.png b/docs/_static/images/vs_code_debug.png
similarity index 100%
rename from docs/images/vs_code_debug.png
rename to docs/_static/images/vs_code_debug.png
diff --git a/docs/tutorials/assets/tutorials/installation/windows_bundle_command_terminal.png b/docs/_static/images/windows_bundle_command_terminal.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/windows_bundle_command_terminal.png
rename to docs/_static/images/windows_bundle_command_terminal.png
diff --git a/docs/tutorials/assets/tutorials/installation/windows_bundle_installer_finish.png b/docs/_static/images/windows_bundle_installer_finish.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/windows_bundle_installer_finish.png
rename to docs/_static/images/windows_bundle_installer_finish.png
diff --git a/docs/tutorials/assets/tutorials/installation/windows_bundle_installer_progress.png b/docs/_static/images/windows_bundle_installer_progress.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/windows_bundle_installer_progress.png
rename to docs/_static/images/windows_bundle_installer_progress.png
diff --git a/docs/tutorials/assets/tutorials/installation/windows_bundle_installer_start.png b/docs/_static/images/windows_bundle_installer_start.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/windows_bundle_installer_start.png
rename to docs/_static/images/windows_bundle_installer_start.png
diff --git a/docs/tutorials/assets/tutorials/installation/windows_launch_napari.png b/docs/_static/images/windows_launch_napari.png
similarity index 100%
rename from docs/tutorials/assets/tutorials/installation/windows_launch_napari.png
rename to docs/_static/images/windows_launch_napari.png
diff --git a/docs/_static/version_switcher.json b/docs/_static/version_switcher.json
index d4da23fba..b6372bbf6 100644
--- a/docs/_static/version_switcher.json
+++ b/docs/_static/version_switcher.json
@@ -5,11 +5,26 @@
 		"url": "https://napari.org/dev/"
 	},
 	{
-		"name": "stable (0.5.1)",
-		"version": "0.5.1",
+		"name": "stable (0.5.4)",
+		"version": "0.5.4",
 		"preferred": true,
 		"url": "https://napari.org/stable/"
 	},
+	{
+		"name": "0.5.3",
+		"version": "0.5.3",
+		"url": "https://napari.org/0.5.3/"
+	},
+	{
+		"name": "0.5.2",
+		"version": "0.5.2",
+		"url": "https://napari.org/0.5.2/"
+	},
+	{
+		"name": "0.5.1",
+		"version": "0.5.1",
+		"url": "https://napari.org/0.5.1/"
+	},
 	{
 		"name": "0.5.0",
 		"version": "0.5.0",
diff --git a/docs/_templates/calendar-template.html b/docs/_templates/calendar-template.html
new file mode 100644
index 000000000..341927529
--- /dev/null
+++ b/docs/_templates/calendar-template.html
@@ -0,0 +1,9 @@
+<nav class="bd-docs-nav bd-links">
+    <div class="bd-toc-item navbar-nav">
+        <ul class="nav bd-sidenav">
+            <li class="toctree-l1">
+                <a class="reference internal" href="community/meeting_schedule.html">Community calendar</a>
+            </li>
+        </ul>
+    </div>
+</nav>
diff --git a/docs/_toc.yml b/docs/_toc.yml
index 1a3502ccd..def47b479 100644
--- a/docs/_toc.yml
+++ b/docs/_toc.yml
@@ -75,6 +75,58 @@ subtrees:
       - file: further-resources/napari-workshops
       - file: further-resources/sample_data
       - file: gallery
+      - file: release/index
+        subtrees:
+        - entries:
+          - file: release/release_0_5_4
+          - file: release/release_0_5_3
+          - file: release/release_0_5_2
+          - file: release/release_0_5_1
+          - file: release/release_0_5_0
+          - file: release/release_0_4_19
+          - file: release/release_0_4_18
+          - file: release/release_0_4_17
+          - file: release/release_0_4_16
+          - file: release/release_0_4_15
+          - file: release/release_0_4_14
+          - file: release/release_0_4_13
+          - file: release/release_0_4_12
+          - file: release/release_0_4_11
+          - file: release/release_0_4_10
+          - file: release/release_0_4_9
+          - file: release/release_0_4_8
+          - file: release/release_0_4_7
+          - file: release/release_0_4_6
+          - file: release/release_0_4_5
+          - file: release/release_0_4_4
+          - file: release/release_0_4_3
+          - file: release/release_0_4_2
+          - file: release/release_0_4_1
+          - file: release/release_0_4_0
+          - file: release/release_0_3_8
+          - file: release/release_0_3_7
+          - file: release/release_0_3_6
+          - file: release/release_0_3_5
+          - file: release/release_0_3_4
+          - file: release/release_0_3_3
+          - file: release/release_0_3_2
+          - file: release/release_0_3_1
+          - file: release/release_0_3_0
+          - file: release/release_0_2_12
+          - file: release/release_0_2_11
+          - file: release/release_0_2_10
+          - file: release/release_0_2_9
+          - file: release/release_0_2_8
+          - file: release/release_0_2_7
+          - file: release/release_0_2_6
+          - file: release/release_0_2_5
+          - file: release/release_0_2_4
+          - file: release/release_0_2_3
+          - file: release/release_0_2_1
+          - file: release/release_0_2_0
+          - file: release/release_0_1_5
+          - file: release/release_0_1_3
+          - file: release/release_0_1_0
   - file: plugins/index
     subtrees:
     - entries:
@@ -178,55 +230,6 @@ subtrees:
           - file: naps/7-key-binding-dispatch
           - file: naps/8-telemetry
           - file: naps/9-multiple-canvases
-      - file: release/index
-        subtrees:
-        - entries:
-          - file: release/release_0_5_1
-          - file: release/release_0_5_0
-          - file: release/release_0_4_19
-          - file: release/release_0_4_18
-          - file: release/release_0_4_17
-          - file: release/release_0_4_16
-          - file: release/release_0_4_15
-          - file: release/release_0_4_14
-          - file: release/release_0_4_13
-          - file: release/release_0_4_12
-          - file: release/release_0_4_11
-          - file: release/release_0_4_10
-          - file: release/release_0_4_9
-          - file: release/release_0_4_8
-          - file: release/release_0_4_7
-          - file: release/release_0_4_6
-          - file: release/release_0_4_5
-          - file: release/release_0_4_4
-          - file: release/release_0_4_3
-          - file: release/release_0_4_2
-          - file: release/release_0_4_1
-          - file: release/release_0_4_0
-          - file: release/release_0_3_8
-          - file: release/release_0_3_7
-          - file: release/release_0_3_6
-          - file: release/release_0_3_5
-          - file: release/release_0_3_4
-          - file: release/release_0_3_3
-          - file: release/release_0_3_2
-          - file: release/release_0_3_1
-          - file: release/release_0_3_0
-          - file: release/release_0_2_12
-          - file: release/release_0_2_11
-          - file: release/release_0_2_10
-          - file: release/release_0_2_9
-          - file: release/release_0_2_8
-          - file: release/release_0_2_7
-          - file: release/release_0_2_6
-          - file: release/release_0_2_5
-          - file: release/release_0_2_4
-          - file: release/release_0_2_3
-          - file: release/release_0_2_1
-          - file: release/release_0_2_0
-          - file: release/release_0_1_5
-          - file: release/release_0_1_3
-          - file: release/release_0_1_0
       - file: roadmaps/index
         subtrees:
         - entries:
diff --git a/docs/community/governance.md b/docs/community/governance.md
index bd105d120..b8fef1b56 100644
--- a/docs/community/governance.md
+++ b/docs/community/governance.md
@@ -74,7 +74,7 @@ developer community (including the SC members) fails to reach such a consensus
 in a reasonable timeframe, the SC is the entity that resolves the issue.
 
 Members of the SC also have the "owner" role within the [napari GitHub organization](https://github.com/napari)
-and are ultimately responsible for managing the napari GitHub account, the [@napari_imaging](https://twitter.com/napari_imaging)
+and are ultimately responsible for managing the napari GitHub account, the [@napari_imaging](https://x.com/napari_imaging)
 twitter account, the [napari website](https://napari.org), and other similar napari owned resources.
 
 The SC will be no less than three members and no more than five members,
diff --git a/docs/community/index.md b/docs/community/index.md
index 878f2e09c..7f170f827 100644
--- a/docs/community/index.md
+++ b/docs/community/index.md
@@ -5,13 +5,32 @@ There are several different ways to be a part of the napari community. From
 being a code or documentation contributor, to creating educational content or
 examples, you are welcome to help develop and improve napari.
 
+## Questions
+
 To ask questions and interact with the team, you can join our
 [zulip chat](https://napari.zulipchat.com/login/) or participate in our
 [meetings](meeting-schedule).
 
+To ask general questions about napari usage to the community, including plugins,
+you can visit ![forum image.sc logo](../images/image_sc_logo.png) [forum.image.sc/tag/napari](https://forum.image.sc/tag/napari)
+
+## News and updates
+
+To trace latest news from napari you may follow us on:
+ * ![twitter logo](../images/twitter_logo.svg) twitter/X [napari_imaging](https://x.com/napari_imaging/) 
+ * ![mastodon logo](../images/mastodon_logo.svg) mastodon [fosstodon.org/@napari](https://fosstodon.org/@napari)    
+
+
+## Contributing and Bug reporting
+
+The napari development happens in the napari GitHub repository [github.com/napari/napari](https://github.com/napari/napari). 
+If you spot a bug, please check our [issues list](https://github.com/napari/napari/issues) . If you 
+do not find a matching report, please open a new issue. 
+
 If you are interested in contributing, check out our
-[contributing guide](contributing).
+[contributing guide](napari-contributing).
 
+## Blog
 To read announcements, learn more about who is using napari and see what our
 community has to say, check out our blog, the
 [Island Dispatch](https://napari.org/island-dispatch).
\ No newline at end of file
diff --git a/docs/community/mission_and_values.md b/docs/community/mission_and_values.md
index 9a187af72..76998e9cc 100644
--- a/docs/community/mission_and_values.md
+++ b/docs/community/mission_and_values.md
@@ -76,4 +76,4 @@ As noted above, we'll be beginning to actively work on the plugin infrastructure
 
 ## Acknowledgements
 
-We share a lot of our mission and values with the `scikit-image` project with whom we share founding members, and acknowledge the influence of their [mission and values statement](https://scikit-image.org/docs/dev/values.html) on this document.
+We share a lot of our mission and values with the `scikit-image` project with whom we share founding members, and acknowledge the influence of their [mission and values statement](https://scikit-image.org/docs/stable/about/values.html) on this document.
diff --git a/docs/community/team.md b/docs/community/team.md
index b11a1f249..6dc861079 100644
--- a/docs/community/team.md
+++ b/docs/community/team.md
@@ -47,7 +47,7 @@ You can read a full history of the project’s founding and early development in
 
 Over time, napari has grown to over 80 direct contributors. Talley Lambert, from Harvard Medical School, began contributing around the time of Juan's blog post, and has been a critical driver of napari's development ever since. We have core developers located in three continents and three biweekly community calls spread across the day to try to accommodate users and contributors in any time zone.
 
-Read more about napari’s [mission and values](https://napari.org/community/mission_and_values.html), how to get started as a [contributor](https://napari.org/developers/contributing.html) or join us in our [zulip chat](https://napari.zulipchat.com/login/) for a more synchronous conversation. You can also follow us on [twitter](https://twitter.com/napari_imaging).
+Read more about napari’s [mission and values](https://napari.org/stable/community/mission_and_values.html), how to get started as a [contributor](https://napari.org/stable/developers/contributing.html) or join us in our [zulip chat](https://napari.zulipchat.com/login/) for a more synchronous conversation. You can also follow us on [twitter](https://x.com/napari_imaging).
 
 ## Institutional and funding Partners
 
diff --git a/docs/conf.py b/docs/conf.py
index ab41f4d30..ba1867796 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -130,6 +130,11 @@
     "footer_end": ["napari-copyright"],
 }
 
+html_sidebars = {
+    "**": ["search-field.html", "sidebar-nav-bs"],
+    "index": ["search-field.html" , "calendar-template"],
+}
+
 html_context = {
    # use Light theme only, don't auto switch (default)
    "default_mode": "light"
@@ -139,7 +144,7 @@
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
 html_static_path = ['_static']
-html_logo = "images/logo.png"
+html_logo = "_static/images/logo.png"
 html_sourcelink_suffix = ''
 html_title = 'napari'
 
@@ -276,7 +281,7 @@ def napari_scraper(block, block_vars, gallery_conf):
     """
     imgpath_iter = block_vars['image_path_iterator']
 
-    if app := napari.qt.get_app():
+    if app := napari.qt.get_qapp():
         app.processEvents()
     else:
         return ""
@@ -294,6 +299,29 @@ def napari_scraper(block, block_vars, gallery_conf):
 
     return scrapers.figure_rst(img_paths, gallery_conf['src_dir'])
 
+from sphinx_gallery import gen_rst
+
+gen_rst.EXAMPLE_HEADER = """
+.. DO NOT EDIT.
+.. THIS FILE WAS AUTOMATICALLY GENERATED BY SPHINX-GALLERY.
+.. TO MAKE CHANGES, EDIT THE SOURCE PYTHON FILE:
+.. "{0}"
+.. LINE NUMBERS ARE GIVEN BELOW.
+
+.. only:: html
+
+    .. note::
+        :class: sphx-glr-download-link-note
+
+        :ref:`Go to the end <sphx_glr_download_{1}>`
+        to download the full example as a Python script or as a
+        Jupyter notebook.{2}
+
+.. rst-class:: sphx-glr-example-title
+
+.. _sphx_glr_{1}:
+
+"""
 
 sphinx_gallery_conf = {
     # path to your example scripts (this value is set in the Makefile)
@@ -301,7 +329,7 @@ def napari_scraper(block, block_vars, gallery_conf):
     'gallery_dirs': 'gallery',  # path to where to save gallery generated output
     'filename_pattern': '/*.py',
     'ignore_pattern': 'README.rst|/*_.py',
-    'default_thumb_file': Path(__file__).parent / 'images' / 'logo.png',
+    'default_thumb_file': Path(__file__).parent / '_static' / 'images' / 'logo.png',
     'plot_gallery': "'True'",  # https://github.com/sphinx-gallery/sphinx-gallery/pull/304/files
     'download_all_examples': False,
     'min_reported_time': 10,
@@ -410,12 +438,23 @@ def get_attributes(item, obj, modulename):
 autosummary_ignore_module_all = False
 
 linkcheck_anchors_ignore = [r'^!', r'L\d+-L\d+', r'r\d+', r'issuecomment-\d+']
-
 linkcheck_ignore = [
-    'https://napari.zulipchat.com/',
-    '../_tags',
-    'https://en.wikipedia.org/wiki/Napari#/media/File:Tabuaeran_Kiribati.jpg',
+    "https://napari.zulipchat.com/",
+    "../_tags",
+    "https://en.wikipedia.org/wiki/Napari#/media/File:Tabuaeran_Kiribati.jpg",
+    "http://localhost:8000",
+    "https://datadryad.org/stash/downloads/file_stream/182482",
+    "https://github.com/napari/docs/issues/new/choose",
+    "https://github.com/napari/napari/issues/new/choose",
+    "https://github.com/napari/napari/issues/new",
+    "https://napari-hub.org",
+    "https://github.com/napari/napari/releases/latest",
+    "https://onlinelibrary.wiley.com/doi/10.1002/col.20327",
 ]
+linkcheck_allowed_redirects = {
+    r"https://youtu\.be/.*": r"https://www\.youtube\.com/.*",
+    r"https://github\.com/napari/napari/releases/download/.*": r"https://objects\.githubusercontent\.com/.*",
+}
 
 
 def rewrite_github_anchor(app, uri: str):
diff --git a/docs/developers/architecture/app_model.md b/docs/developers/architecture/app_model.md
index 4f5cdb534..b03230e66 100644
--- a/docs/developers/architecture/app_model.md
+++ b/docs/developers/architecture/app_model.md
@@ -28,7 +28,7 @@ The {class}`~napari._app_model._app.NapariApplication` (`app`)
 is the top level object that stores information about the commands, keybindings
 and menus that make up the application.
 It is a subclass of {class}`app_model.Application` and is a global application
-singleton. It can be retrieved with `napari._app_model.get_app`.
+singleton. It can be retrieved with `napari._app_model.get_app_model`.
 
 Currently, the primary purpose of the `app` is to compose the following
 {mod}`app_model.registries` into a single name-spaced object:
@@ -106,10 +106,10 @@ The code below shows how to register the `action` defined above with the napari
 singleton `app`:
 
 ```python
-from napari._app_model import get_app
+from napari._app_model import get_app_model
 
 
-get_app().register_action(action)
+get_app_model().register_action(action)
 ```
 
 ````{note}
@@ -395,7 +395,7 @@ current viewer, if one present (returning `None` if not). It is
 registered in the `app.injection_store` via `app.injection_store.register_provider`. Processors can be registered in the same way.
 
 ```python
-from napari._app_model import get_app
+from napari._app_model import get_app_model
 
 # return annotation indicates what this provider provides
 def provide_points() -> Optional['Points']:
@@ -409,7 +409,7 @@ def provide_points() -> Optional['Points']:
             None
         )
 
-get_app().injection_store.register_provider(provide_points)
+get_app_model().injection_store.register_provider(provide_points)
 ```
 
 This allows both internal and external functions to be injected with these
@@ -418,7 +418,7 @@ This is particularly important in a GUI context, where a user can't always be
 providing arguments:
 
 ```python
->>> injected_func = get_app().injection_store.inject(process_points)
+>>> injected_func = get_app_model().injection_store.inject(process_points)
 ```
 
 Note: injection doesn't *inherently* mean that it's always safe to call an
@@ -502,11 +502,11 @@ On `napari` start up, `app-model` initialization occurs in the following order:
 1. Initialize {class}`~napari.viewer.Viewer`, which calls
    `napari.plugins._initialize_plugins`, which registers discovered plugins
    and all their actions (non-Qt first, followed immedidately by Qt actions).
-   This also results in the first call to `napari._app_model.get_app`.
+   This also results in the first call to `napari._app_model.get_app_model`.
 
    i. Instantiation of the `app-model` app results in registration of all non-GUI
       internal `napari` actions (and associated submenus). Note that the
-      `napari._app_model.get_app` call creates the `app` only when *first*
+      `napari._app_model.get_app_model` call creates the `app` only when *first*
       called. It simply returns the existing app on all subsequent calls.
 
 2. {class}`~napari._qt.qt_main_window.Window` instantiation, followed by
@@ -532,8 +532,8 @@ singleton `app` may keep a reference to an object, e.g., a
 since been cleaned up at the end of a previous test.
 Thus, we mock the `app` in a `_mock_app` fixture, and
 explicitly use it in {ref}`make_napari_viewer` as well as in all tests that
-use the `get_app` function. This way, a new instance of `app` is returned
-every time `napari._app_model.get_app`
+use the `get_app_model` function. This way, a new instance of `app` is returned
+every time `napari._app_model.get_app_model`
 is used inside a test. This 'test' `app` is available for use throughout the test's
 duration and will get cleaned up at the end.
 
diff --git a/docs/developers/architecture/dir_organization.md b/docs/developers/architecture/dir_organization.md
index 2848ee08b..ffe62c855 100644
--- a/docs/developers/architecture/dir_organization.md
+++ b/docs/developers/architecture/dir_organization.md
@@ -73,7 +73,7 @@ is named `_qapp_model` inside `_qt/`).
   canvas (the canvas is a vispy object onto which you can draw 'visuals').
 * `benchmarks/` - benchmarking code, mostly for checking the performance of layers.
   It is is executed in CI and is run every Sunday. See
-  [`.github/workflows/benchmarks.yml`](https://github.com/napari/napari/tree/main/.github/workflows/benchmarks.yml)
+  [`.github/workflows/benchmarks.yml`](https://github.com/napari/napari/blob/main/.github/workflows/benchmarks.yml)
   for CI workflow details. The benchmarks can also be run locally.
 * `components/` - code that defines all components of the napari viewer, including the
   layerlist, dimensions and camera.
diff --git a/docs/developers/contributing/dev_install.md b/docs/developers/contributing/dev_install.md
index b85896834..b128d3c70 100644
--- a/docs/developers/contributing/dev_install.md
+++ b/docs/developers/contributing/dev_install.md
@@ -1,7 +1,7 @@
 (dev-installation)=
 ## Setting up a development installation
 
-In order to make changes to `napari`, you will need to [fork](https://docs.github.com/en/get-started/quickstart/contributing-to-projects#forking-a-repository) the
+In order to make changes to `napari`, you will need to [fork](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project) the
 [repository](https://github.com/napari/napari). If you are not familiar with `git`, we recommend reading up on [this guide](https://docs.github.com/en/get-started/using-git/about-git#basic-git-commands).
 
 1. Clone the forked repository to your local machine and change directories:
@@ -22,7 +22,7 @@ In order to make changes to `napari`, you will need to [fork](https://docs.githu
     ::::{tab-set}
 
     :::{tab-item} Using `conda`
-    After [installing `conda`](https://www.anaconda.com/products/distribution), create an environment called `napari-env` with Python {{ python_version }} and activate it.
+    After [installing `conda`](https://www.anaconda.com/download), create an environment called `napari-env` with Python {{ python_version }} and activate it.
 
     {{ conda_create_env }}
     :::
@@ -74,7 +74,7 @@ In order to make changes to `napari`, you will need to [fork](https://docs.githu
 
 5. We use [`pre-commit`](https://pre-commit.com) to format code with
    [`black`](https://github.com/psf/black) and lint with
-   [`ruff`](https://github.com/charliermarsh/ruff) automatically prior to each commit.
+   [`ruff`](https://github.com/astral-sh/ruff) automatically prior to each commit.
    To minimize test errors when submitting pull requests, please install `pre-commit`
    in your environment as follows:
 
@@ -88,7 +88,7 @@ In order to make changes to `napari`, you will need to [fork](https://docs.githu
    see [`black`'s documentation](https://black.readthedocs.io/en/stable/).
 
    Code will also be linted to enforce the stylistic and logistical rules specified
-   in our [`flake8` configuration](https://github.com/napari/napari/blob/main/setup.cfg), which currently ignores
+   in our [`flake8` configuration](https://github.com/napari/napari/blob/main/pyproject.toml), which currently ignores
    [E203](https://lintlyci.github.io/Flake8Rules/rules/E203.html),
    [E501](https://lintlyci.github.io/Flake8Rules/rules/E501.html),
    [W503](https://lintlyci.github.io/Flake8Rules/rules/W503.html) and
diff --git a/docs/developers/contributing/documentation/docs_deployment.md b/docs/developers/contributing/documentation/docs_deployment.md
index 0cf5a6efe..228748f0f 100644
--- a/docs/developers/contributing/documentation/docs_deployment.md
+++ b/docs/developers/contributing/documentation/docs_deployment.md
@@ -55,7 +55,7 @@ through several CI workflows detailed below.
       turn happens on every commit to the `main` branches of either
       `napari/napari` or `napari/docs`).
     - For every commit to the `gh-pages` branch of this repo, the
-      [`unversioned_pages.yml` action](https://github.com/napari/napari.github.io/blob/main/.github/workflows/unversioned_pages.yml)
+      [`unversioned_pages.yml` action](https://github.com/napari/napari.github.io/blob/gh-pages/.github/workflows/unversioned_pages.yml)
       is triggered and copies the latest contents of the index page and the dev
       folder over the "stable" version of the documentation. This ensures that
       both the landing page of the website and the developer documentation,
diff --git a/docs/developers/contributing/documentation/index.md b/docs/developers/contributing/documentation/index.md
index f8796fe30..965b0063d 100644
--- a/docs/developers/contributing/documentation/index.md
+++ b/docs/developers/contributing/documentation/index.md
@@ -40,7 +40,7 @@ by either [uploading file(s) from your computer](https://docs.github.com/en/repo
 [creating and editing a new file](https://docs.github.com/en/repositories/working-with-files/managing-files/creating-new-files)
 or [editing an existing file](https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files)
 on the [napari/docs](https://github.com/napari/docs) GitHub repository.
-It's best if you first [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the [napari/docs](https://github.com/napari/docs) repository to your own GitHub account, create a [feature branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch), upload/create/edit files through the GitHub web interface, and then [open a pull request from your fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) back to [napari-docs](https://github.com/napari/docs).
+It's best if you first [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) the [napari/docs](https://github.com/napari/docs) repository to your own GitHub account, create a [feature branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch), upload/create/edit files through the GitHub web interface, and then [open a pull request from your fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) back to [napari-docs](https://github.com/napari/docs).
 
 You will also be able to [preview the documentation](doc_view_ci) as it would appear on [napari.org](https://napari.org/dev) by
 using the `Check the rendered docs here!` action at the bottom of your PR which will go to a preview site on [CircleCI](https://circleci.com/).
@@ -397,22 +397,22 @@ you will only be able to preview the documentation on CircleCI.
 Simply click on **Details** next to the `Check the rendered docs here!` at the bottom
 of your pull request:
 
-![CircleCI check is highlighted](images/circleci-link.png)
+![CircleCI check is highlighted](../../../_static/images/circleci-link.png)
 
 #### Download documentation artifact
 
 1. Click on **Details** next to
    `Build & Deploy PR Docs / Build & Upload Artifact (pull_request)`:
 
-![The "Build & Deploy PR Docs / Build & Upload Artifact" check is highlighted](images/doc-ci-1.png)
+![The "Build & Deploy PR Docs / Build & Upload Artifact" check is highlighted](../../../_static/images/doc-ci-1.png)
 
 2. Click on **Summary** on the top left corner:
 
-![Summary link in the "Build & Deploy PR Docs / Build & Uplod Artifact" GitHub Action page](images/doc-ci-2.png)
+![Summary link in the "Build & Deploy PR Docs / Build & Uplod Artifact" GitHub Action page](../../../_static/images/doc-ci-2.png)
 
 3. Scroll down to **Artifacts** and click on **html** to download the built documentation:
 
-!["html" link in the Artifacts section of the "Build & Deploy PR Docs / Build & Uplod Artifact" GitHub Action page is highlighted](images/doc-ci-3.png)
+!["html" link in the Artifacts section of the "Build & Deploy PR Docs / Build & Uplod Artifact" GitHub Action page is highlighted](../../../_static/images/doc-ci-3.png)
 
 4. Extract the compressed archive and open the `html/index.html` file on your preferred browser.
    You can also use Python's `http.server` module to open a local server on
@@ -487,7 +487,7 @@ If you are using an IDE, it is likely that it will not use Git Bash by default.
 Alternatively, you can install WSL, which will allow you to run a Linux environment directly on Windows (without any virtual machines, etc.). You need to have Windows 10 version 2004 and higher or Windows 11. Then you can run scripts and command line utilities, as well as python and napari from for example Ubuntu on your Windows machine.
 
 1. Install the [Windows Subsystem for Linux](https://learn.microsoft.com/en-us/windows/wsl/install) and [choose a linux distribution](https://learn.microsoft.com/en-us/windows/wsl/install#change-the-default-linux-distribution-installed).
-We will use Ubuntu for this guide since it is the default WSL distribution, easy to install, and works well with [WSLg](https://github.com/microsoft/wslg). The default method to perform this installation is to run `wsl --install -d Ubuntu` from command prompt as an administrator but you can refer to the [guide](https://docs.microsoft.com/en-us/windows/wsl/install-win10) for other installation methods.
+We will use Ubuntu for this guide since it is the default WSL distribution, easy to install, and works well with [WSLg](https://github.com/microsoft/wslg). The default method to perform this installation is to run `wsl --install -d Ubuntu` from command prompt as an administrator but you can refer to the [guide](https://learn.microsoft.com/en-us/windows/wsl/install) for other installation methods.
 2. Restart your computer. On restart, you will be prompted to create a user account for WSL. This account is separate from your Windows account, but you can use the same username and password if you wish.
 3. [Open up the Ubuntu distribution](https://learn.microsoft.com/en-us/windows/wsl/install#ways-to-run-multiple-linux-distributions-with-wsl) via the `Ubuntu` command and run `sudo apt update && sudo apt upgrade` to update the distribution.
 4. Install a napari development environment in Ubuntu following the [contributor guide](dev-installation) and activate the virtual environment that napari was installed into.
diff --git a/docs/developers/contributing/index.md b/docs/developers/contributing/index.md
index 4bf587b24..16932fd15 100644
--- a/docs/developers/contributing/index.md
+++ b/docs/developers/contributing/index.md
@@ -17,7 +17,7 @@ The first step to make changes to napari is to
 set up a [napari development installation](dev-installation).
 
 You can then use git to save your changes and open a
-[pull-request](https://docs.github.com/en/get-started/quickstart/contributing-to-projects#making-a-pull-request) (PR) via the following steps:
+[pull-request](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project) (PR) via the following steps:
 
 1. Make and save your changes:
 
@@ -46,7 +46,7 @@ To set it, use `git config --global user.email your-address@example.com`.
 2. Share your changes:
 
 To push the local changes in your new feature branch to your
-[forked](https://docs.github.com/en/get-started/quickstart/contributing-to-projects#forking-a-repository) repository:
+[forked](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project#forking-a-repository) repository:
 
 ```sh
 git push -u origin your-branch-name
@@ -63,7 +63,7 @@ git remote -vv
 ```
 
 You can then make a
-[PR](https://docs.github.com/en/get-started/quickstart/contributing-to-projects#making-a-pull-request) to `napari`'s `main` branch.
+[PR](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project#making-a-pull-request) to `napari`'s `main` branch.
 
 ## napari contribution guides
 
diff --git a/docs/developers/contributing/performance/benchmarks.md b/docs/developers/contributing/performance/benchmarks.md
index e40f00b8c..45b1367c6 100644
--- a/docs/developers/contributing/performance/benchmarks.md
+++ b/docs/developers/contributing/performance/benchmarks.md
@@ -102,6 +102,31 @@ of time since building napari can be a time consuming task:
 asv run -E existing -b ViewImageSuite
 ```
 
+## Debugging a benchmark
+
+To run a benchmark in a debugger, you can use the command:
+
+```bash
+python -m pdb napari/benchmarks/benchmark_file.py BenchmarkClass.benchmark_method
+```
+or 
+```bash
+python -m pdb -m napari.benchmarks benchmark_file.BenchmarkClass.benchmark_method
+```
+
+For example, to debug the ``time_set_view_slice`` method in the ``Image2DSuite``
+benchmark, you can run:
+
+```bash
+python -m pdb napari/benchmarks/benchmark_image_layer.py Image2DSuite.time_set_view_slice
+```
+or 
+
+```bash
+python -m pdb -m napari.benchmarks benchmark_image_layer.Image2DSuite.time_set_view_slice
+```
+
+
 ## Comparing results to main
 
 Often, the goal of a PR is to compare the results of the modifications in terms
diff --git a/docs/developers/contributing/testing.md b/docs/developers/contributing/testing.md
index 2e9b9320b..d2853e95a 100644
--- a/docs/developers/contributing/testing.md
+++ b/docs/developers/contributing/testing.md
@@ -29,7 +29,7 @@ much as we can with unit tests, requiring fewer integration tests, and the least
 of functional tests as depicted in the test pyramid below from
 [softwaretestinghelp.com](https://www.softwaretestinghelp.com/the-difference-between-unit-integration-and-functional-testing/):
 
-![Pyramid diagram depicting the relationship between time to write/execute three different types of tests and return on investment for those tests.  The pyramid is split into three sections: the bottom, largest section is Unit testing, the middle section is Integration testing and the top is Functional testing. The size of the section is proportional to the quantity of tests of that type you should write. Moving up the pyramid, tests take longer to write and have a lower return on investment.](../../images/tests.png)
+![Pyramid diagram depicting the relationship between time to write/execute three different types of tests and return on investment for those tests.  The pyramid is split into three sections: the bottom, largest section is Unit testing, the middle section is Integration testing and the top is Functional testing. The size of the section is proportional to the quantity of tests of that type you should write. Moving up the pyramid, tests take longer to write and have a lower return on investment.](../../_static/images/tests.png)
 
 Unit tests are at the base of the pyramid because they are the easiest to write and
 the quickest to run. The time and effort to implement and maintain tests increases
@@ -205,48 +205,118 @@ you create during testing need to be cleaned up at the end of each test. We thus
 recommend that you use the following fixtures when needing a widget or
 {class}`~napari.Viewer` in a test.
 
-#### qtbot
+#### qapp and qtbot
 
-If you need a `QApplication` to be running for your test, you can use the
+If you need to use any Qt related code in your test, you need to ensure that
+a `QApplication` is created. To to this we suggest you use the
+[`qapp`](https://pytest-qt.readthedocs.io/en/latest/reference.html#module-pytestqt.plugin)
+fixture from [`pytest-qt`](https://pytest-qt.readthedocs.io/en/latest/index.html),
+a napari testing dependency.
+
+If you need to instantiate a Qt GUI object (e.g., a widget) for your test, we recommend
+that you use the
 [`qtbot`](https://pytest-qt.readthedocs.io/en/latest/reference.html#pytestqt.qtbot.QtBot)
-fixture from `pytest-qt`, a napari testing dependency.
+fixture. `qtbot`, which itself depends on `qapp` , allows you to test user input
+(e.g., mouse clicks) by sending events to Qt objects.
 
 ````{note}
 Fixtures in pytest can be a little mysterious, since it's not always
-clear where they are coming from.  In this case using the `pytest-qt` `qtbot`fixture
-looks like this:
+clear where they are coming from.  The `pytest-qt` `qapp` and `qtbot` fixtures
+can be used in two ways; by adding them to the list of arguments of your test function:
 
 ```python
-# just by putting `qtbot` in the list of arguments
-# pytest-qt will start up an event loop for you
 def test_something(qtbot):
     ...
 ```
+or by using pytest's `usefixtures`, which avoids adding an unused argument to your
+test function:
+
+```python
+@pytest.mark.usefixtures('qtbot')
+def test_something():
+    ...
+```
 <br/>
 ````
 
-`qtbot` provides a convenient
-[`addWidget`](https://pytest-qt.readthedocs.io/en/latest/reference.html#pytestqt.qtbot.QtBot.addWidget)
-method that will ensure that the widget gets closed at the end of the test.
-It *also* provides a whole bunch of other
-convenient methods for interacting with your GUI tests (clicking, waiting
-signals, etc...).  See the [`qtbot` docs](https://pytest-qt.readthedocs.io/en/latest/reference.html#pytestqt.qtbot.QtBot) for details.
+`qtbot` also provides a convenient
+[`add_widget`/`addWidget`](https://pytest-qt.readthedocs.io/en/latest/reference.html#pytestqt.qtbot.QtBot.addWidget)
+method that will ensure that the widget gets closed and properly cleaned at the end
+of the test. This can prevents segfaults when running several tests. The
+[`wait_until`/`waitUntil`](https://pytest-qt.readthedocs.io/en/latest/reference.html#pytestqt.qtbot.QtBot.waitUntil)
+method is also useful to wait for a desired condition. The example below
+adds a `QtDims` widget, plays the `Dims` and checks that the `QtDim` widget
+is playing before we make any assertions.
 
 ```python
-# the qtbot provides convenience methods like addWidget
 def test_something_else(qtbot):
-    widget = QWidget()
-    qtbot.addWidget(widget)  # tell qtbot to clean this widget later
+    dims = Dims(ndim=3, ndisplay=2, range=((0, 10, 1), (0, 20, 1), (0, 30, 1)))
+    view = QtDims(dims)
+    qtbot.addWidget(view)
+    # Loop to prevent finishing before the assertions in this test.
+    view.play(loop_mode='loop')
+    qtbot.waitUntil(lambda: view.is_playing)
     ...
 ```
 
+(qt_viewer)=
+#### `qt_viewer` and `viewer_model`
+
+Since `napari==0.5.4` we have implemented the `qt_viewer` [pytest fixture](https://docs.pytest.org/en/stable/explanation/fixtures.html) which can be used for tests that are only using the `ViewerModel` api or are only checking rendering of the viewer. 
+For the current moment, it is only for internal use and is not exported to the global scope, 
+as it is defined in `conftest.py` file. 
+
+The `qt_viewer` fixture returns the instance of the {class}`~napari.qt.QtViewer` class.
+This class does not provide the same api as the {class}`~napari.ViewerModel` class, 
+but has an associated {class}`~napari.ViewerModel` instance, which can be accessed by the `viewer` attribute.
+Alternatively, you could use the `viewer_model` fixture, which returns this instance of {class}`~napari.ViewerModel` class.
+
+```python
+def test_something(qt_viewer):
+    qt_viewer.viewer.add_image(np.random.random((10, 10)))
+    assert len(viewer.layers) == 1
+    assert viewer.layers[0].name == 'Image'
+```
+
+or 
+
+```python
+def test_something(qt_viewer, viewer_model):
+    viewer_model.add_image(np.random.random((10, 10)))
+    assert len(viewer.layers) == 1
+    assert viewer.layers[0].name == 'Image'
+```
+
+The `qt_viewer` fixture takes care of proper teardown of all qt widgets related to the viewer.
+If you need to adjust the QtViewer for a given [test file](https://docs.pytest.org/en/stable/how-to/fixtures.html#override-a-fixture-on-a-test-module-level) you can use the `qt_viewer_` fixture.
+
+```python
+@pytest.fixture
+def qt_viewer(qt_viewer_):
+    # in this file we need to have added data and 3d view for all tests in file
+    qt_viewer_.viewer.add_image(np.random.random((5, 10, 10)))
+    qt_viewer_.viewer.dims.ndisplay = 3
+    return qt_viewer_
+```
+
+or 
+
+```python
+@pytest.fixture
+def qt_viewer(qt_viewer_):
+    # Make bigger viewer for all tests in file
+    qt_viewer_.setGeometry(0, 0, 1000, 1000)
+    return qt_viewer_
+```
+
+
 (make_napari_viewer)=
 #### `make_napari_viewer`
 
-We provide a
-[pytest fixture](https://docs.pytest.org/en/stable/explanation/fixtures.html) called
-`make_napari_viewer` for tests that require the {class}`~napari.Viewer`. This
-fixture is available globally and to all tests in the same environment that `napari`
+For more complex test cases where we need to fully test application behaviour 
+(for example, using the `viewer.window` API) we can use `make_napari_viewer` [pytest fixture](https://docs.pytest.org/en/stable/explanation/fixtures.html).
+However, the creating and teardown of the whole viewer is more fragile and slower than using just the `qt_viewer` fixture.
+This fixture is available globally and to all tests in the same environment that `napari`
 is in (see [](test-organization) for details). Thus, there is no need to import it,
 you simply include `make_napari_viewer` as a test function parameter, as shown in the
 **Examples** section below:
@@ -304,7 +374,7 @@ you patch or replace parts of the code being tested with "fake" behavior or
 return values, so that you can test how a given function would perform *if* it
 were to receive some value from the upstream code.  For a few examples of using
 mocks when testing napari, search the codebase for
-[`unittest.mock`](https://github.com/napari/napari/search?q=%22unittest.mock%22&type=Code)
+[`unittest.mock`](https://github.com/search?q=repo%3Anapari%2Fnapari+%22unittest.mock%22&type=Code)
 
 ## Known issues
 
diff --git a/docs/developers/coredev/core_dev_guide.md b/docs/developers/coredev/core_dev_guide.md
index eafd6fa10..f386b963f 100644
--- a/docs/developers/coredev/core_dev_guide.md
+++ b/docs/developers/coredev/core_dev_guide.md
@@ -180,7 +180,7 @@ As a core member, you should be familiar with the following napari guides:
 ### Social resources
 
 - [#napari on image.sc](https://forum.image.sc/tag/napari).
-- [#napari](https://twitter.com/search?q=%23napari&f=live) and [@napari_imaging](https://twitter.com/napari_imaging) on twitter.
+- [#napari](https://x.com/search?q=%23napari&f=live) and [@napari_imaging](https://x.com/napari_imaging) on twitter.
 - [napari zulip](https://napari.zulipchat.com/) community chat channel.
 
 You are not required to monitor the social resources.
diff --git a/docs/developers/coredev/maintenance.md b/docs/developers/coredev/maintenance.md
index 73c55a4a3..810434514 100644
--- a/docs/developers/coredev/maintenance.md
+++ b/docs/developers/coredev/maintenance.md
@@ -10,9 +10,8 @@ Because of the security GitHub policy, the commits and pull requests created by
 will not trigger another action's runs. The possible workaround for this is to close and then reopen the pull request.
 But this requires additional actions by core devs.
 
-
 To get automatically running workflows, we need to create a personal access token (PAT) and add it to the repository secrets.
-For security reasons, it is recommended to create a [fine-grained token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token). It allows us to provide only the required permissions.
+For security reasons, it is recommended to create a [fine-grained token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). It allows us to provide only the required permissions.
 
 The token should have a one-year expiration date. After that, it needs to be refreshed.
 
@@ -22,18 +21,18 @@ The token should be named `GHA_TOKEN` and the required permissions are:
  * **read and write** to pull requests
  * **read and write** to code
 
- ![screenshot of token permissions in GitHub UI](../../images/update_token_permissions.png)
+ ![screenshot of token permissions in GitHub UI](../../_static/images/update_token_permissions.png)
 
  At the moment of writing this document, there is a difference in names between the summary of the token and the list of permissions.
  The **code** permission is called **Contents** in the Edit view of the token.
 
-![screenshot of token permissions](../../images/edit_token_permissions.png)
+![screenshot of token permissions](../../_static/images/edit_token_permissions.png)
 
 ## Refreshing the token
 
 To create a new token, go to the personal settings page and select _Developer settings_ at the bottom of the left menu. On the visible screen, expand the _Personal access tokens_ section and click the _Fine-grained token_ link.
 
-![View on list of fine-grained tokens](../../images/fine_grained_token.png)
+![View on list of fine-grained tokens](../../_static/images/fine_grained_token.png)
 
 Then click the _Generate new token_ button in the upper right corner.
 
@@ -48,11 +47,11 @@ Fill the form:
 4. Select **napari** to be the resource owner
 5. Select _Only selected repositories_ and then select **napari/napari** repository
 
-![screenshot of the token creation form](../../images/token_permission_form.png)
+![screenshot of the token creation form](../../_static/images/token_permission_form.png)
 
 6. Select the required permissions for repository metadata, pull requests, and code (contents)
 
-![screenshot of the token creation form](../../images/token_permission_selection.png)
+![screenshot of the token creation form](../../_static/images/token_permission_selection.png)
 
 7. Click the _Generate token_ button
 8. Copy token
@@ -60,8 +59,35 @@ Fill the form:
 10. Expand the _Secrets and variables_ section and select _Actions_
 11. Click the edit button for the `GHA_TOKEN` secret
 
-![screenshot of the token creation form](../../images/secrets_section.png)
+![screenshot of the token creation form](../../_static/images/secrets_section.png)
 
 12. Paste a new token to the value field
 
 To validate if the token is working, you can run the "Upgrade test constraints" workflow manually. Ensure that there will be some packages to update.
+
+## Update translation strings
+
+Currently, translations are unmaintained, but this may change in the future as napari matures.
+
+As new code is included in the codebase, some of the strings that need to be translated might
+not yet be using the `trans` methods. To help keep the codebase up to date in terms
+of translations we added a test script that
+[runs daily on CI](https://github.com/napari/napari/actions/workflows/test_translations.yml)
+and can be also run locally to ensure that a release includes the most up to date translatable
+strings.
+
+The test script is available on the `/tools/validate_strings.py` file and it relies on an additional
+file `/tools/strings_list.py` to include strings to skip safely from translation.
+
+The test checks:
+
+  1. **Untranslated strings**: not using the `trans` methods.
+  2. **Outdated skip strings**: should no longer be included in the `/tools/strings_list.py` file.
+  3. **Translation usage errors**: where translation strings may be missing interpolation variables.
+
+You can execute tests locally from the repository root, and follow the instructions printed
+on the `stdout` if any test fails.
+
+  ```bash
+  pytest tools/ --tb=short
+  ```
\ No newline at end of file
diff --git a/docs/developers/coredev/packaging.md b/docs/developers/coredev/packaging.md
index 2451d8c9f..f0de8409d 100644
--- a/docs/developers/coredev/packaging.md
+++ b/docs/developers/coredev/packaging.md
@@ -173,6 +173,10 @@ The main OS-agnostic keys are:
 
 Then, depending on the operating systems and the installer format, we customize the configuration a bit more.
 
+The bundled Python version in the installers follows the Python version installed in the CI
+`make_bundle_conda.yml` workflow at `napari/packaging`. Update the CI matrix configuration to bump
+the bundled Python. We use the oldest version supported by the [SPEC-0][SPEC0] recommendations.
+
 #### Default installation path
 
 This depends on each OS. Our general strategy is to put the general installation under
@@ -251,7 +255,7 @@ Generating a `conda`-based installer requires several components in place:
 [4]: https://github.com/pypa/gh-action-pypi-publish
 [6]: https://github.com/conda/constructor
 [7]: https://conda.github.io/constructor/construct-yaml/
-[8]: https://conda-forge.org/docs/maintainer/updating_pkgs.html#rerendering-feedstocks
+[8]: https://conda-forge.org/docs/maintainer/updating_pkgs/#rerendering-feedstocks
 [16]: https://github.com/conda-forge/napari-feedstock/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Aclosed
 [17]: https://anaconda.org/napari
 [19]: https://nsis.sourceforge.io/Main_Page
@@ -259,3 +263,4 @@ Generating a `conda`-based installer requires several components in place:
 [21]: https://anaconda.org/conda-forge/napari
 [22]: https://github.com/conda/constructor/blob/764ba8a/constructor/nsis/_nsis.py
 [nap-2]: https://napari.org/dev/naps/2-conda-based-packaging.html
+[SPEC0]: https://scientific-python.org/specs/spec-0000/
diff --git a/docs/developers/coredev/release.md b/docs/developers/coredev/release.md
index b96602d5d..608af78cc 100644
--- a/docs/developers/coredev/release.md
+++ b/docs/developers/coredev/release.md
@@ -2,52 +2,52 @@
 
 # Release guide
 
-This guide documents `napari`'s release process.
-Currently, it only handles distribution, but as the project matures,
-it will include generating release notes, documentation, etc.
+This guide documents `napari`'s release process. Most required tools mentioned here are in https://github.com/napari/napari-release-tools
 
 # Timeline
-New versions of `napari` will be released every two months. The first release candidate will be available one week prior to release for testing purposes. Multiple release candidates may become available during the week prior to release. Upcoming releases can be found in our public calendar.
+
+Currently, we are releasing a new napari version every 2-3 weeks. Release candidates are made available as a reasonableness check for 1-24h before the full release is published: since the release cadence is so high, any new bugs can be quickly rectified, and more quickly identified by making a full release.
+
+When major API changes and deprecations happen, we will provide longer release candidate cycles to ensure proper testing by the community.
 
 The latest release candidate can be installed with
 
 `python -m pip install --pre napari`
 
 # Release management
-The release will be coordinated by a release manager whose responsibilities include...
+The release will be coordinated by a release manager whose responsibilities include the following.
 
-## Two weeks before release (one week before release candidate)
-- Look through currently open PRs and get a sense of what would be good to merge before the first release candidate
-- Ensure `conda-recipe/meta.yaml` in `napari/packaging` is up-to-date (e.g. `run` dependencies match `setup.cfg` requirements).
-- Create a zulip thread in the release channel letting people know the release candidate is coming and pointing out PRs that would be nice to merge before release
+## One week before release
+- Look through currently open PRs and get a sense of what would be good to merge before the first release candidate. Set milestones appropriately;
+- Ensure `conda-recipe/meta.yaml` in `napari/packaging` is up-to-date (e.g. `run` dependencies match `pyproject.toml` requirements);
+- Create a zulip thread in [the release channel](https://napari.zulipchat.com/#narrow/stream/215289-release) letting people know the release candidate is coming and pointing out PRs that would be nice to merge before release.
 
-At this stage, bug fixes and features that are close to landing should be prioritized. The release manager will follow up with PR authors, reviewing and merging as needed.
+At this stage, bug fixes and features that are close to landing should be prioritized. The release manager will follow up with PR authors, reviewing and merging as needed. New features should wait until after release.
 
-## Nine days before release (two days before release candidate)
-- Generate release notes with the script in the release folder
-- Fill in the release highlights and make a PR with the release notes
+## 1-2 days before release
 
-At this point the release manager should ideally be the only person merging PRs on the repo for the next week.
+- Add a header and highlights section to the [`additional notes`](https://github.com/napari/napari-release-tools/tree/main/additional_notes) folder for the given release. Use the [highlight label](https://github.com/napari/napari/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aopen+label%3Ahighlight) for the relevant milestone to note which PRs to comment on.
+- Generate release notes with the [`generate_release_notes.py` script from napari/napari-release-tools](https://github.com/napari/napari-release-tools/blob/main/generate_release_notes.py);
+- make a PR with the release notes, making sure to add the new document to the [napari/docs table of contents file](https://github.com/napari/docs/blob/main/docs/_toc.yml). See an example of such a PR: [https://github.com/napari/docs/pull/485](https://github.com/napari/docs/pull/485)
 
-## One week before release
-- Add any recently merged PRs to release notes
-- Merge release notes
-- Make the release candidate
-- Announce to release stream on zulip that the first release candidate is available for testing
+At this point the release manager should ideally be the only person merging PRs on the repo for the next few days before the release.
 
-## The week before release
-- Merge any PRs and update release notes accordingly
-- Make new release candidates as necessary and announce them on zulip
+## 1-0 days before release
 
-At this stage PRs merged should focus mainly on regressions and bug fixes. New features should wait until after release.
+- Merge any remaining PRs and update release notes accordingly;
+- Merge release notes;
+- Make the release candidate and announce on zulip;
+- Announce to release stream on zulip that the first release candidate is available for testing.
 
 ## The day of release
-- make sure final rc has been tested
-- ensure all PRs have been added to release notes and then make release and announce on zulip
+- Make sure final rc has been tested;
+- Ensure all PRs have been added to release notes;
+- Make sure docs are correctly deployed;
+- Make release and announce on zulip.
 
 # Release process
 
-Additional `release` dependencies (`python -m pip install -e .[release]`) are required to complete the release process.
+Additional `release` dependencies (`python -m pip install -e .[release]`, from the `napari/napari` root folder) are required to complete the release process.
 
 > [`MANIFEST.in`](https://github.com/napari/napari/blob/main/MANIFEST.in) determines which non-Python files are included.
 > Make sure to check that all necessary ones are listed before beginning the release process.
@@ -55,7 +55,7 @@ Additional `release` dependencies (`python -m pip install -e .[release]`) are re
 The `napari/napari` repository must have a PyPI API token as a GitHub secret.
 This likely has been done already, but if it has not, follow
 [this guide](https://pypi.org/help/#apitoken) to gain a token and
-[this guide](https://docs.github.com/en/actions/security-guides/encrypted-secrets)
+[this guide](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions)
 to add it as a secret.
 
 ## Determining the version
@@ -70,15 +70,19 @@ release though we need to generate the release notes.
 
 ## Generating release notes
 
-1. Make a list of merges, contributors, and reviewers by running
-   ``python docs/release/generate_release_notes.py -h`` and following that file's usage.
+1. Grab the `generate_release_notes.py` script from the
+   [napari/napari-release-tools](https://github.com/napari/napari-release-tools)
+   repo. Make a list of merges, contributors, and reviewers by running
+   ``python generate_release_notes.py -h`` and following that file's usage.
    For each release generate the list to include everything since the last release for which there
-   are release notes (which should just be the last release). For example making the release notes
-   for the `0.2.1` release can be done as follows:
+   are release notes (which should just be the last release). To substitute GitHub handles for author names, use the `--correction-file` option.
+
+   For example, to create release notes for the `0.5.4` release, use:
 
    ```bash
-   python docs/release/generate_release_notes.py v0.2.0 main --version 0.2.1 | tee docs/release/release_0_2_1.md
+   python generate_release_notes.py 0.5.4 --target-directory=/path/to/docs/release/ --correction-file /path/to/name_corrections.yaml
    ```
+   See [name_corrections.yaml](https://github.com/napari/napari-release-tools/blob/main/name_corrections.yaml).
 
 2. Scan the PR titles for highlights, deprecations, API changes,
    and bugfixes, and mention these in the relevant sections of the notes.
@@ -90,30 +94,23 @@ release though we need to generate the release notes.
 
 4. Make and merge a PR with these release notes before moving onto the next steps.
 
-## Update translation strings
+## Update constraints files
 
-As new code is included in the codebase, some of the strings that need to be translated might
-not yet be using the `trans` methods. To help keep the codebase up to date in terms
-of translations we added a test script that
-[runs daily on CI](https://github.com/napari/napari/actions/workflows/test_translations.yml)
-and can be also run locally to ensure that a release includes the most up to date translatable
-strings.
+`napari` uses a set of constraints files to prevent test failures due to dependency updates. This also allows for reproducible builds (see [](dev-installation)).
+These constraints files need to be updated at least weekly on Monday, and may also be triggered manually by a maintainer. You can find these files at
+[resources/constraints](https://github.com/napari/napari/tree/main/resources/constraints).
 
-The test script is available on the `/tools/test_strings.py` file and it relies on an additional
-file `/tools/strings_list.py` to include strings to skip safely from translation.
+To get updated constraints for a PR, use `@napari-bot update constraints` in a PR comment, then follow the instruction added by the bot to the conversation.
 
-The test checks:
+````{admonition} Example
+To update the docs constraints file, assuming you have the `napari/napari` repo and `napari/docs` repo cloned next to each other, you can install [uv](https://astral.sh/blog/uv) and run the following command from the root of the `napari` repo:
 
-  1. **Untranslated strings**: not using the `trans` methods.
-  2. **Outdated skip strings**: should no longer be included in the `/tools/strings_list.py` file.
-  3. **Translation usage errors**: where translation strings may be missing interpolation variables.
-
-You can execute tests locally from the repository root, and follow the instructions printed
-on the `stdout` if any test fails.
+```bash
+uv pip compile --python-version 3.11 --upgrade --output-file resources/constraints/constraints_py3.11_docs.txt pyproject.toml resources/constraints/version_denylist.txt resources/constraints/version_denylist_examples.txt ../docs/requirements.txt resources/constraints/pydantic_le_2.txt --extra pyqt5 --extra pyqt6 --extra pyside2 --extra pyside6_experimental --extra testing --extra testing_extra --extra optional
+```
+````
 
-  ```bash
-  pytest tools/ --tb=short
-  ```
+To see other examples, check out the [upgrade test constraints action](https://github.com/napari/napari/blob/main/.github/workflows/upgrade_test_constraints.yml).
 
 ## Tagging the new release candidate
 
@@ -170,11 +167,14 @@ git tag vX.Y.Z main
 git push upstream --tags
 ```
 
+Once the new tag is pushed, the [`make_release.yml` workflow](https://github.com/napari/napari/blob/main/.github/workflows/make_release.yml) will be triggered, using the [PyPI Publish action](https://github.com/pypa/gh-action-pypi-publish) to publish the new napari version to PyPI using [Trusted Publishers](https://docs.pypi.org/trusted-publishers/).
+
 ## conda-forge packages
 
 The packages on `conda-forge` are not controlled directly by our repositories.
 Instead, they are governed by the `conda-forge/napari-feedstock` repository.
 The essential actions are automated, but there are a few maintenance notes we need to have in mind.
+For a more complete description of the napari packaging infrastructure, see {ref}`napari-packaging`.
 
 ### New releases
 
@@ -186,15 +186,16 @@ Before merging, please pay special attention to these aspects:
 
 - Version string has been correctly updated. The build number should have been reset to `0` now.
 - The CI passes correctly. Do check the logs, especially the test section (search for `TEST START`).
-- The `run` dependencies match the runtime requirements of the PyPI release (listed in `setup.cfg`).
+- The `run` dependencies in `recipe/meta.yaml` match the runtime requirements of the PyPI release (listed in `pyproject.toml`).
   Watch for modified version constraints, as well as added or removed packages.
   Note that the `conda-forge` packages include some more dependencies for convenience,
-  so you might need to check the `extras` sections in `setup.cfg`.
+  so you might need to check the `optional` sections in `pyproject.toml`.
 
 ```{note}
 See these PRs for examples on previous conda-forge releases:
 - [napari v0.4.16](https://github.com/conda-forge/napari-feedstock/pull/41)
 - [napari v0.4.17](https://github.com/conda-forge/napari-feedstock/pull/42)
+- [napari v0.5.3](https://github.com/conda-forge/napari-feedstock/pull/68)
 ```
 
 ### Patch dependencies of previous releases
@@ -227,3 +228,23 @@ For more details, follow the instructions for
 ["Mark packages as broken on conda-forge"](https://github.com/conda-forge/admin-requests#mark-packages-as-broken-on-conda-forge).
 
 Please make sure a correct build for the problematic release is available before (or shortly after) the `admin-requests` PR is merged!
+
+## Post release: update the documentation
+
+The [napari docs](https://napari.org) are versioned, meaning that each release has its own documentation, selected throught the version switcher dropdown. Once you tag a new version in the `napari/napari` repo, the [`build_and_deploy.yml` workflow](https://github.com/napari/docs/blob/main/.github/workflows/build_and_deploy.yml) will automatically create a new folder for this version number in the `gh-pages` branch of the `napari/napari.github.io` repo.
+
+Next, you need to do the following:
+
+1. In the `napari/napari.github.io` repo, update the `stable` symlink in the `gh-pages` branch to point to the new version. This can be done by running the following commands in the `napari/napari.github.io` repo:
+
+```bash
+git checkout gh-pages
+rm stable
+ln -s X.Y.Z stable
+git add stable
+git commit -m "Update stable symlink to X.Y.Z"
+git push
+```
+
+2. In the `napari/docs` repo, update the [`docs/_static/version_switcher.json` file](https://github.com/napari/docs/blob/main/docs/_static/version_switcher.json) so that `stable` points to the right version. The active version switcher is read from the file in the `dev` folder, so this can be done as the last step in the process.
+
diff --git a/docs/developers/index.md b/docs/developers/index.md
index ca93c790f..2ff65c59d 100644
--- a/docs/developers/index.md
+++ b/docs/developers/index.md
@@ -24,7 +24,7 @@ napari has a [Code of Conduct](napari-coc) that should be honored by everyone wh
   onboarding new core developers:
   - [Core Developer guide](core-dev-guide)
   - [Maintenance](napari-maintenance)
-  - [Release guide](release)
+  - [Release guide](napari-release)
   - [Deploying documentation](docs-deployment)
   - [Packaging](napari-packaging)
 
@@ -37,6 +37,6 @@ There are a number of ways to contact the napari community:
 - [zulip](https://napari.zulipchat.com/): the zulip napari community chat channel.
 - [GitHub issue](https://github.com/napari/napari/issues): feel free to open an
   issue in our GitHub repository. Issues and pull-requests are written in [Markdown](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github). You can find a comprehensive guide [here](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
-- [Image.sc forum](https://forum.image.sc/tags/napari): napari is a community partner
+- [Image.sc forum](https://forum.image.sc/tag/napari): napari is a community partner
   on the Image.sc forum. All usage support requests should be posted on the forum with
   the tag "napari".
diff --git a/docs/further-resources/glossary.md b/docs/further-resources/glossary.md
index db3b7bbbb..4bf05c126 100644
--- a/docs/further-resources/glossary.md
+++ b/docs/further-resources/glossary.md
@@ -3,20 +3,20 @@
 | napari term        | description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | synonym/closely related term                                                |
 |--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|
 | canvas             | The canvas in the center of napari viewer contains the visual display of the data passed to napari, including images, points, shapes, and other supported data types.                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                             |
-| channel            | A channel is an image where each pixel only contains its intensity value (i.e. grayscale image). In fluorescence microscopy, each channel corresponds to a range of wavelengths. An RGB image from digital camera consists of 3 channels - red, green, blue (RGB). In napari, an image dimension that is not spatial or temporal can be considered as channels, and is typically represented as individual [image layer](https://napari.org/stable/howtos/layers/image.html). See also [this wiki page](https://en.wikipedia.org/wiki/Channel_(digital_image)) for specific examples.       | raster band in geoscience                                                   |
+| channel            | A channel is an image where each pixel only contains its intensity value (i.e. grayscale image). In fluorescence microscopy, each channel corresponds to a range of wavelengths. An RGB image from digital camera consists of 3 channels - red, green, blue (RGB). In napari, an image dimension that is not spatial or temporal can be considered as channels, and is typically represented as individual [image layer](layers-image). See also [this wiki page](https://en.wikipedia.org/wiki/Channel_(digital_image)) for specific examples.       | raster band in geoscience                                                   |
 | colormap           | A colormap represents the value of each pixel as a particular color. In fluorescence microscopy, the colormap can be selected to mirror the color of the collected wavelength. In other applications, colormaps can be used to provide the visual representation of the measured signal. There are many different types of colormaps available, see [choosing colormaps in matplotlib](https://matplotlib.org/stable/tutorials/colors/colormaps.html).                                                                                                                                                                                                                                                                                                                                                                    | look up table, LUT                                                          |
-| event              | Events and connections are a way to tell napari "If this event occurs, then call this function". [Hooking up your own events](https://napari.org/stable/howtos/extending/connecting_events.html).                                                                                                                                                                                                                                                                                               |                                                                             |
-| hook               | Hooks are places in napari where plugins can offer extended functionality. See the [napari hook specification reference](https://napari.org/stable/plugins/npe1.html#hook-specification-reference) in the [napari plugin documentation](https://napari.org/stable/plugins/index.html).                                                                                                                                                                                                                                                                                               |                                                                             |
-| hook specification | A function signature that defines the application programming interface (API) that a plugin developer must adhere to when writing the function that napari promises to call somewhere in the napari codebase. See also [napari hook specifications](https://napari.org/stable/plugins/npe1.html#hook-specification-reference).                                                                                                                                                                                                                                                                             |                                                                             |
-| keybinding         | The specific key or key combination that when pressed causes some function to occur. For example, command/control + C triggers "copy" in many operating systems. You can make your own custom keybindings, see this page on [hooking up your own events](https://napari.org/stable/howtos/extending/connecting_events.html).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | keyboard short cut                                                          |
-| mousebinding       | The specific mouse move, click, or drag event that causes some function to occur. You can make your own custom mousebindings, see this page on [hooking up your own events](https://napari.org/stable/howtos/extending/connecting_events.html).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | mouse short cut                                                             |
-| layer              | Layers are the viewable objects that can be added to napari viewer. Currently napari supports the following layers: [image](https://napari.org/stable/howtos/layers/image.html), [labels](https://napari.org/stable/howtos/layers/labels.html), [points](https://napari.org/stable/howtos/layers/points.html), [shapes](https://napari.org/stable/howtos/layers/shapes.html), [surface](https://napari.org/stable/howtos/layers/surface.html), [tracks](https://napari.org/stable/howtos/layers/tracks.html), [vectors](https://napari.org/stable/howtos/layers/vectors.html). |                                                                             |
-| label              | A label is a region of an integer image where the pixels are the same unique value. It is implemented in napari in the [labels layer](https://napari.org/stable/howtos/layers/labels.html) where each label represents a unique object, feature or classification.                                                                                                                                                                                                                                                                                                                         |                                                                             |
-| point              | A point is defined by the coordinate in space. The [points layer](https://napari.org/stable/howtos/layers/points.html)  allows you to display an NxD array of N points in D coordinates.                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                             |
-| shape              | Shapes are visual representations of N points in D coordinates. Shapes can be used as a visualization tool to indicate region of interest (ROI) or for downstream operations. In napari, the [shapes layer](https://napari.org/stable/howtos/layers/shapes.html) is a viewable object that permits visualization of the following supported shapes: rectangle, ellipses, polygons, paths, and lines.                                                                                                                                                                                                                 | [area selection tools in ImageJ](https://imagej.nih.gov/ij/docs/tools.html) |
-| surface            | A surface comprises a set of triangles (typically in three dimensions) that are connected by their common edges or corners to form the mesh. See [napari surface layer tutorial](https://napari.org/stable/howtos/layers/surface.html) for current implementation and [this wiki page](https://en.wikipedia.org/wiki/Surface_triangulation) for additional information.                                                                                                                                                                                                                    |                                                                             |
-| track              | A track describes object trajectories along the time dimension. The [tracks layer](https://napari.org/stable/howtos/layers/tracks.html) defines a track by the list containing object coordinates and the time point, with each track assigned a unique track ID.                                                                                                                                                                                                                                                                                                                              |                                                                             |
-| vector             | A vector is a line defined by its start and end positions in space. The [vectors layer](https://napari.org/stable/howtos/layers/vectors.html) renders lines onto the canvas, with input data format as Nx2xD numpy array representing N vectors in D dimensions.                                                                                                                                                                                                                                                                                                                               |                                                                             |
+| event              | Events and connections are a way to tell napari "If this event occurs, then call this function". [Hooking up your own events](connecting-events).                                                                                                                                                                                                                                                                                               |                                                                             |
+| hook               | Hooks are places in napari where plugins can offer extended functionality. See the [napari hook specification reference](hook-specifications-reference) in the [napari plugin documentation](plugins-index).                                                                                                                                                                                                                                                                                               |                                                                             |
+| hook specification | A function signature that defines the application programming interface (API) that a plugin developer must adhere to when writing the function that napari promises to call somewhere in the napari codebase. See also [napari hook specifications](hook-specifications-reference).                                                                                                                                                                                                                                                                             |                                                                             |
+| keybinding         | The specific key or key combination that when pressed causes some function to occur. For example, command/control + C triggers "copy" in many operating systems. You can make your own custom keybindings, see this page on [hooking up your own events](connecting-events).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | keyboard short cut                                                          |
+| mousebinding       | The specific mouse move, click, or drag event that causes some function to occur. You can make your own custom mousebindings, see this page on [hooking up your own events](connecting-events).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | mouse short cut                                                             |
+| layer              | Layers are the viewable objects that can be added to napari viewer. Currently napari supports the following layers: [image](layers-image), [labels](layers-labels), [points](layers-points), [shapes](layers-shapes), [surface](layers-surface), [tracks](layers-tracks), [vectors](layers-vectors). |                                                                             |
+| label              | A label is a region of an integer image where the pixels are the same unique value. It is implemented in napari in the [labels layer](layers-labels) where each label represents a unique object, feature or classification.                                                                                                                                                                                                                                                                                                                         |                                                                             |
+| point              | A point is defined by the coordinate in space. The [points layer](layers-points)  allows you to display an NxD array of N points in D coordinates.                                                                                                                                                                                                                                                                                                                                                                                                       |                                                                             |
+| shape              | Shapes are visual representations of N points in D coordinates. Shapes can be used as a visualization tool to indicate region of interest (ROI) or for downstream operations. In napari, the [shapes layer](layers-shapes) is a viewable object that permits visualization of the following supported shapes: rectangle, ellipses, polygons, paths, and lines.                                                                                                                                                                                                                 | [area selection tools in ImageJ](https://imagej.net/ij/docs/tools) |
+| surface            | A surface comprises a set of triangles (typically in three dimensions) that are connected by their common edges or corners to form the mesh. See [napari surface layer tutorial](layers-surface) for current implementation and [this wiki page](https://en.wikipedia.org/wiki/Surface_triangulation) for additional information.                                                                                                                                                                                                                    |                                                                             |
+| track              | A track describes object trajectories along the time dimension. The [tracks layer](layers-tracks) defines a track by the list containing object coordinates and the time point, with each track assigned a unique track ID.                                                                                                                                                                                                                                                                                                                              |                                                                             |
+| vector             | A vector is a line defined by its start and end positions in space. The [vectors layer](layers-vectors) renders lines onto the canvas, with input data format as Nx2xD numpy array representing N vectors in D dimensions.                                                                                                                                                                                                                                                                                                                               |                                                                             |
 | widget             | A small, composable graphical user interface component that can extend user's ability to interact with layers and other napari functions. A widget could be a simple one parameter/control (e.g. a button) or a collection of multiple controls with data output.                                                                                                                                                                                                                                                                                                                                                                                                              | [dialog in ImageJ](https://imagej.net/scripting/generic-dialog)             |
 | dock widget        | A widget that can be attached (docked) to the main napari viewer at a specified position.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                             |
-| plugin             | A napari plugin is a specialized Python package that extends napari's functionality. Examples of extended functionality include: additional file i/o support, image analysis, and other utilities. Plugin developers specify this functionality through a combination of Python entry points and a specialized manifest file. Plugins for napari can be found at [napari hub](https://www.napari-hub.org/). For a guide on how to make your own custom plugin, see [creating a napari plugin](https://napari.org/stable/plugins/index.html).                                                                                                                                                                                 |                                                                             |
+| plugin             | A napari plugin is a specialized Python package that extends napari's functionality. Examples of extended functionality include: additional file i/o support, image analysis, and other utilities. Plugin developers specify this functionality through a combination of Python entry points and a specialized manifest file. Plugins for napari can be found at [napari hub](https://www.napari-hub.org/). For a guide on how to make your own custom plugin, see [creating a napari plugin](plugins-index).                                                                                                                                                                                 |                                                                             |
diff --git a/docs/further-resources/napari-workshops.md b/docs/further-resources/napari-workshops.md
index 8f4448d73..3e4b8704d 100644
--- a/docs/further-resources/napari-workshops.md
+++ b/docs/further-resources/napari-workshops.md
@@ -22,10 +22,19 @@ or contact the core developers on [zulip chat](https://napari.zulipchat.com/logi
 ## Workshops
 
 *Workshops are listed from newest to oldest.*
+* October 2023, Halfway to I2K
+  * [An updated general napari
+    workshop](https://kephale.github.io/napari-workshop-halfway-to-i2k/home.html). Note
+    that this workshop has the first workshop version of how to make your
+    interactive segmentation tool in napari.
+
 * September 2023
   * [Plugin design](https://chanzuckerberg.github.io/napari-plugin-accel-workshops/workshops/design23.html) and [software development workshop](https://chanzuckerberg.github.io/napari-plugin-accel-workshops/workshops/softwaredev.html) for [napari plugin grantees](https://chanzuckerberg.com/rfa/napari-plugin-grants/).
   * [Bioimage Analysis with Python and Napari (video lecture)](https://www.youtube.com/watch?v=QDS5t7oZH-c) at the [EMBO Practical Course for Advanced Methods in Bioimage Analysis](https://www.embl.org/about/info/course-and-conference-office/events/bia23-01/)  
   
+* July 2023, Microscopy and Microanalysis 2023
+  * [napari for electron microscopy](https://kephale.github.io/napari-workshop-mandm-2023/home.html)
+
 * November 2022, napari foundation grant onboarding
   * [Getting started with napari plugin development slide deck](https://docs.google.com/presentation/d/15lrFRLPm9bfmU4hgcVwoduIJr5bqhoHo7ZeWLO6H_Us/edit?usp=sharing)
   * [Watch it here](https://drive.google.com/file/d/1IYDV-GTGEYh5j_tvBaWYEZ_tQXTqmJkr/view?usp=share_link)
@@ -33,11 +42,11 @@ or contact the core developers on [zulip chat](https://napari.zulipchat.com/logi
 
 * September 2022, Helmholtz Imaging Summer Academy
   * [Image analysis with Python and Napari](https://biapol.github.io/HIP_Introduction_to_Napari_and_image_processing_with_Python_2022/intro.html)
-  * [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.7102242.svg)](https://doi.org/10.5281/zenodo.7102242)
+  * [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.7102242.svg)](https://zenodo.org/records/7102242)
 
 * July 2022, SciPy 2022
   * [watch it here](https://www.youtube.com/watch?v=vismuuc4y1I&list=PLYx7XA2nY5Gfxu98P_HL1MnFb_BSkpxLV&index=10)
-  * [Workshop materials available here](https://alisterburt.github.io/napari-workshops/SciPy-0722/intro.html)
+  * [Workshop materials available here](http://alisterburt.com/napari-workshops/SciPy-0722/intro.html)
 
 * January to May 2022, [accelerator grantee plugin workshop](https://chanzuckerberg.github.io/napari-plugin-accel-workshops/)
 
@@ -54,7 +63,7 @@ or contact the core developers on [zulip chat](https://napari.zulipchat.com/logi
   * [Slide available here](https://docs.google.com/presentation/d/1sqd_CYckEwmgQO6y9VffwnmT0RSlRYIAUBixRTMYcig/view)
 
 * August 2021, [NDCN](https://chanzuckerberg.com/science/programs-resources/neurodegeneration-challenge/) Workshop / September 2021 [ZIDAS](https://www.zidas.org/) Workshop
-  * [Read the workshop materials online](https://alisterburt.github.io/napari-workshops/home.html)
+  * [Read the workshop materials online](http://alisterburt.com/napari-workshops/home.html)
   * [Workshop materials available here](https://github.com/alisterburt/napari-workshops)
 
 * June 2021, Bioimage analysis fundamentals in Python workshop at [SciPy 2021](https://www.scipy2021.scipy.org/)
diff --git a/docs/further-resources/sample_data.md b/docs/further-resources/sample_data.md
index 40c0712a5..a1c04b8e2 100644
--- a/docs/further-resources/sample_data.md
+++ b/docs/further-resources/sample_data.md
@@ -10,7 +10,7 @@ If you come across image databases that are missing from the list below, create
 |------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [Allen Brain Atlases](http://portal.brain-map.org)                                        | Human and mouse brain atlas containing gene expression, anatomic, and genomic data                                                                                                            |
 | [Allen Cell Explorer](https://www.allencell.org)                                        | Database of cell data, segmentations, and analyses with multiple experimental parameters.                                                                                                     |
-| [Berkeley Drosophila Genome Project (BDGP) in situ database](http://insitu.fruitfly.org/cgi-bin/ex/insitu.pl) | Patterns of gene expression in Drosophila embryogenesis.                                                                                                                                      |
+| [Berkeley Drosophila Genome Project (BDGP) in situ database](https://insitu.fruitfly.org/cgi-bin/ex/insitu.pl) | Patterns of gene expression in Drosophila embryogenesis.                                                                                                                                      |
 | [The Cell Image Library](http://www.cellimagelibrary.org/home)                                     | Public resource database of images, videos, and animations of cells, capturing a wide diversity of organisms, cell types, and cellular processes.                                             |
 | [FlyLight Imagery](https://open.quiltdata.com/b/janelia-flylight-imagery)                                           | 3D fly's central nervous system captured by confocal laser scanning microscope.                                                                                                               |
 | [OpenCell](https://opencell.czbiohub.org/download)                                                   | A proteome-scale collection of protein localization and interaction measurements in human cells. Contains fluorescence microscopy and IP-MS data.                                             |
@@ -18,11 +18,11 @@ If you come across image databases that are missing from the list below, create
 | [BioImage Archive](https://www.ebi.ac.uk/biostudies/bioimages/studies)                                           | Description and data of biological studies; links to databases at EMBL-EBI (European Molecular Biology Laboratory–European Bioinformatics Institute).                                         |
 | [Image Data Resource (IDR)](https://idr.openmicroscopy.org)                                  | Public data repository for storing and integrating image data sets from published scientific studies.                                                                                         |
 | [Systems Science of Biological Dynamics (SSBD)](https://ssbd.riken.jp/database/)              | Set of quantitative data and microscopy images from a variety of species, sources, and methods.                                                                                               |
-| [Cancer Imaging Archive](https://www.cancerimagingarchive.net/collections/)                                     | Collections of cancer medical images.                                                                                                                                                         |
+| [Cancer Imaging Archive](https://www.cancerimagingarchive.net/browse-collections/)                                     | Collections of cancer medical images.                                                                                                                                                         |
 | [Brain Image Library](https://www.brainimagelibrary.org/)                                        | A public resource to deposit, analyze, mine, share, and interact with large brain image datasets.                                                                                             |
 | [EMPIAR](https://www.ebi.ac.uk/empiar/)                                                     | The Electron Microscopy Public Image Archive (EMPIAR) is a public resource for raw images underpinning 3D cryo-EM maps and tomograms.                                                         |
 | [OME-NGFF files on IDR](https://idr.github.io/ome-ngff-samples/)                                      | Catalog of IDR images formatted as OME-NGFF.                                                                                                                                                  |
-| [Cell Tracking Challenge](http://celltrackingchallenge.net/datasets)                                    | Repository of annotated videos from the Cell Tracking Challenge; contains contrast-enhancing (PhC, DIC) or fluorescence (widefield, confocal, multiphoton, and light sheet microsocopy) data. |
+| [Cell Tracking Challenge](https://celltrackingchallenge.net/datasets)                                    | Repository of annotated videos from the Cell Tracking Challenge; contains contrast-enhancing (PhC, DIC) or fluorescence (widefield, confocal, multiphoton, and light sheet microsocopy) data. |
 | [Bio-Formats supported formats](https://docs.openmicroscopy.org/bio-formats/6.9.1/supported-formats.html)                              | Example files for Bio-Formats supported formats.                                                                                                                                              |
 | [BioImage Informatics Index (BIII) datasets](http://biii.eu/dataset)                 | Mix of datasets and links to other data repositories.                                                                                                                                         |
 | [SCIFIO](https://scif.io/images/)                                                     | Example images with CC0 licenses.                                                                                                                                                             |
diff --git a/docs/gallery.md b/docs/gallery.md
index e3d857c9f..310010e90 100644
--- a/docs/gallery.md
+++ b/docs/gallery.md
@@ -3,6 +3,10 @@
 
 Examples of napari usage.
 
+All examples in this gallery can be downloaded as Python scripts or Jupyter
+notebooks to be executed locally. Check out [](launch-jupyter) for more details
+on using napari in Jupyter notebooks.
+
 ```{note}
 
 If you want to submit a new example to this gallery, check out our
diff --git a/docs/guides/3D_interactivity.md b/docs/guides/3D_interactivity.md
index 509691cbd..5fef7f1cd 100644
--- a/docs/guides/3D_interactivity.md
+++ b/docs/guides/3D_interactivity.md
@@ -5,12 +5,12 @@
 ## Coordinate systems in napari
 In napari, there are three main coordinate systems: (1) canvas, (2) world, and (3) layer. The canvas coordinates system is the 2D coordinate system of the canvas on which the scene is rendered. World coordinates are the nD coordinates of the entire scene. As the name suggests, layer coordinates are the nD coordinate system of the data in a given layer. Layer coordinates are specific to each layer's data and are related to the world coordinate system via the layer transforms.
 
-![A diagram of the coordinate systems and components involved when interacting with layers in napari. The camera faces the 3D scene to generate a 2D image that is presented on the canvas.](images/3d_interaction_coordianates.png)
+![A diagram of the coordinate systems and components involved when interacting with layers in napari. The camera faces the 3D scene to generate a 2D image that is presented on the canvas.](../_static/images/3d_interaction_coordianates.png)
 
 ## In 3D mode, clicks are lines
 Since the 3D scene is rendered on a 2D surface (your screen), your mouse click does not map to a specific point in space. As the view is a [parallel projection](https://en.wikipedia.org/wiki/Parallel_projection), napari can determine a line through 3D space that intersects the canvas where the user clicked.
 
-![A diagram that shows how clicking on a 2D position on the canvas corresponds to a 3D click line in the scene that starts from the 3D camera position.](images/3d_interaction_click_line.png)
+![A diagram that shows how clicking on a 2D position on the canvas corresponds to a 3D click line in the scene that starts from the 3D camera position.](../_static/images/3d_interaction_click_line.png)
 
 When a user clicks or moves the mouse in the canvas, napari emits a mouse event with the following properties:
 
@@ -25,7 +25,7 @@ When a user clicks or moves the mouse in the canvas, napari emits a mouse event
 ## Determining where the click intersects the data
 Each napari layer has a method called `get_ray_intersections()` that will return the points on the data bounding box that a given line will intersect (`start_point ` and `end_point `). When the click line (`view_direction`) and position (`position`) are used as inputs, `start_point` and `end_point` are the end points of the segment click line that intersects the layer's axis-alinged data bounding box. `start_point` is the end point that is closest to the camera (i.e, the "first" intersection) and `end_point` is the end point that is farthest from the camera (i.e., the "last" intersection). You can use the line segment between `start_point` and `end_point` to interrogate the layer data that is "under" your cursor.
 
-![A diagram that shows how the 3D click line starting from the camera position intersects with the 3D bounding box associated with a layer's data. There are two intersection points. A start point, which is the first intersection point, and the end point which is the second.](images/3d_interaction_ray_intersection.png)
+![A diagram that shows how the 3D click line starting from the camera position intersects with the 3D bounding box associated with a layer's data. There are two intersection points. A start point, which is the first intersection point, and the end point which is the second.](../_static/images/3d_interaction_ray_intersection.png)
 
 See the `get_ray_intersection()` docstrings below for details. Note that if the line does not intersect the data bounding box (i.e., the click was outside of the data), `start_point` and `end_point` are `None`. The `position` and `view_direction` should be provided as world coordinates if `world` is set to True and in layer coordinates if `world` is set to `False`.
 
diff --git a/docs/guides/contexts_expressions.md b/docs/guides/contexts_expressions.md
index ecf4ccd8a..deb770ceb 100644
--- a/docs/guides/contexts_expressions.md
+++ b/docs/guides/contexts_expressions.md
@@ -220,7 +220,7 @@ Out[15]: False
 But unlike a simple string, they can also provide type hinting, linting
 capabilities, and IDE autocompletion (for napari developers).
 
-![An IDE showing a type hint for an attribute of the LayerListContextKeys class.](images/context_type_hint.png)
+![An IDE showing a type hint for an attribute of the LayerListContextKeys class.](../_static/images/context_type_hint.png)
 
 A record of all registered context keys can be retrieved with the class method
 `ContextKey.info()`
diff --git a/docs/guides/event_loop.md b/docs/guides/event_loop.md
index bfb646c87..7c6232863 100644
--- a/docs/guides/event_loop.md
+++ b/docs/guides/event_loop.md
@@ -19,9 +19,9 @@ connect events to "callback" functions, which essentially specifies; "If this ev
 happens, then call this function". Next you start the event loop and hope you
 connected everything correctly!  Indeed, much of the napari source code is
 dedicated to creating and handling events: search the codebase for
-[`.emit(`](https://github.com/napari/napari/search?q=%22.emit%28%22&type=code)
+[`.emit(`](https://github.com/search?q=repo%3Anapari%2Fnapari+%22.emit%28%22&type=code)
 and
-[`.connect(`](https://github.com/napari/napari/search?q=%22.connect%28%22&type=code)
+[`.connect(`](https://github.com/search?q=repo%3Anapari%2Fnapari+%22.connect%28%22&type=code)
 to find examples of creating and handling internal events, respectively.
 
 It is not necessary to have a deep understanding of event loops to use
@@ -139,7 +139,7 @@ If you would like to create your own widgets in napari see {ref}`creating-widget
 ### napari's `QApplication`
 
 In napari, the initial step of creating the `QApplication` is handled by
-{func}`napari.qt.get_app`.  (Note however, that napari will do this for you
+{func}`napari.qt.get_qapp`.  (Note however, that napari will do this for you
 automatically behind the scenes when you create a viewer with
 {class}`napari.Viewer()`)
 
diff --git a/docs/guides/layers.md b/docs/guides/layers.md
index f55b57df9..cb7ab06c0 100644
--- a/docs/guides/layers.md
+++ b/docs/guides/layers.md
@@ -36,13 +36,13 @@ with the layer from the viewer. These modes are accessible via the layer control
 widget top buttons and via keyboard shortcuts (these shortcuts will vary depending on the layer type). Currently, there are two base modes:
 
 * Pan and zoom
-![image: Pan/zoom](../images/pan-zoom-tool.png)
+![image: Pan/zoom](../_static/images/pan-zoom-tool.png)
 
 The `pan_zoom` mode allows you to pan around and zoom in/out the layer. It's
 the default mode selected. Note: zooming with the mouse-wheel should essentially always work!
 
 * Transform
-![image: Transform](../images/transform-tool.png)
+![image: Transform](../_static/images/transform-tool.png)
 
 The `transform` mode allows you to translate, rotate, and scale the layer
 graphically. Note: While you can transform 3D layers, at present this mode is only usable in 2D viewer display mode.
@@ -106,7 +106,7 @@ other layers.
 
 For example, the image below shows an image with the blending set to `additive`.
 
-![napari viewer with an image of a cell. Layer controls are open in the left sidebar with the blending set to additive.](./images/blending.png)
+![napari viewer with an image of a cell. Layer controls are open in the left sidebar with the blending set to additive.](../_static/images/blending.png)
 
 ## 3D rendering of images
 
@@ -154,7 +154,7 @@ distances from the camera according to a maximum intensity projection to create
 the 2D image that is then displayed on the screen. This mode works well for many
 biological images such as these cells growing in culture:
 
-![napari viewer with an image of cells in a culture. Layer controls are open in the left sidebar and rendering set to mip.](./images/rendering.png)
+![napari viewer with an image of cells in a culture. Layer controls are open in the left sidebar and rendering set to mip.](../_static/images/rendering.png)
 
 When viewing 2D slices the rendering mode has no effect.
 
diff --git a/docs/guides/threading.md b/docs/guides/threading.md
index 7527ec931..bb3fe3e63 100644
--- a/docs/guides/threading.md
+++ b/docs/guides/threading.md
@@ -152,6 +152,7 @@ def error_prone_function():
     ...
 ```
 
+(generators-for-the-win)=
 ## Generators for the win!
 
 ````{admonition} quick reminder
diff --git a/docs/howtos/layers/image.md b/docs/howtos/layers/image.md
index bc2e46fdc..ffc43cc93 100644
--- a/docs/howtos/layers/image.md
+++ b/docs/howtos/layers/image.md
@@ -10,7 +10,7 @@ kernelspec:
   language: python
   name: python3
 ---
-(image-layer)=
+(layers-image)=
 # Using the `image` layer
 
 In this document, you will learn how to use the `napari` `image` layer,
@@ -45,11 +45,11 @@ sample image of your choice.
 
 ### Buttons
 
-* `Pan/zoom` ![image: Pan/zoom tool](../../images/pan-zoom-tool.png) is the default mode
+* `Pan/zoom` ![image: Pan/zoom tool](../../_static/images/pan-zoom-tool.png) is the default mode
   of the layer and supports panning and zooming. Press the `1` key when the layer is selected
   to use this mode.
 
-* `Transform` ![image: Transform](../../images/transform-tool.png) enables you to
+* `Transform` ![image: Transform](../../_static/images/transform-tool.png) enables you to
   rotate, scale, or translate the layer. Note: at present this feature is limited to 2D viewer display mode.
   To reset the transformation,
   you can Option/Alt-click the transform button (a confirmation dialog will open to
diff --git a/docs/howtos/layers/labels.md b/docs/howtos/layers/labels.md
index f96995801..3aa85d624 100644
--- a/docs/howtos/layers/labels.md
+++ b/docs/howtos/layers/labels.md
@@ -76,7 +76,7 @@ layer:
 
   Use this tool to manually erase a label on the `labels layer`. Other layers
   will not be affected. The label eraser tool looks like this:
-  ![image: eraser tool](../../images/labels-layer-eraser.png)
+  ![image: eraser tool](../../_static/images/labels-layer-eraser.png)
 
 * **Paintbrush**
 
@@ -260,7 +260,7 @@ mode by pressing the `6` key when the `labels layer` is selected.
 
 ### Transform mode
 
-This mode is represented by ![image: Transform](../../images/transform-tool.png) in the
+This mode is represented by ![image: Transform](../../_static/images/transform-tool.png) in the
 `layer controls` panel. It enables you to rotate, scale, or translate the layer.
 Note: at present this feature is limited to 2D viewer display mode.
 To reset the transformation, you can Option/Alt-click the transform button (a
@@ -476,7 +476,7 @@ and [zarr arrays](https://zarr.readthedocs.io/en/stable/api/core.html). A
 Because the `labels` layer subclasses the `image` layer, it inherits the great
 properties of the `image` layer, like supporting lazy loading and multiscale
 images for big data layers. For more information about both these concepts see
-the details in the [image layer guide](image-layer).
+the details in the [image layer guide](layers-image).
 
 ## Creating a new labels layer
 
@@ -512,8 +512,8 @@ where the data is represented as a multiscale image is not editable.
 
 All layers can be rendered in both 2D and 3D. One of the viewer buttons at the
 bottom of the left panel can toggle between these 2 modes.
-When in 2D, the button looks like this: ![image: 2D/3D button](../../images/3D-button.png), ready to switch to 3D mode.
-When in 3D, the button looks like this: ![image: 2D/3D button](../../images/2D-button.png), ready to switch to 2D mode.
+When in 2D, the button looks like this: ![image: 2D/3D button](../../_static/images/3D-button.png), ready to switch to 3D mode.
+When in 3D, the button looks like this: ![image: 2D/3D button](../../_static/images/2D-button.png), ready to switch to 2D mode.
 
 The number of dimensions sliders will be 2 or 3 less than the total number of
 dimensions of the layer, allowing you to browse volumetric timeseries data and
diff --git a/docs/howtos/layers/points.md b/docs/howtos/layers/points.md
index 6913637dc..a041c8e1a 100644
--- a/docs/howtos/layers/points.md
+++ b/docs/howtos/layers/points.md
@@ -10,7 +10,7 @@ kernelspec:
   language: python
   name: python3
 ---
-
+(layers-points)=
 # Using the `points` layer
 
 ```{Admonition} DEPRECATED ATTRIBUTES
@@ -71,14 +71,14 @@ layer:
 ### Buttons
 
 * **Deleting points**
-  ![image: Delete points tool](../../images/point-deleting-tool.png)
+  ![image: Delete points tool](../../_static/images/point-deleting-tool.png)
 
   Points can be deleted after they have been selected. First select the point or
   points to delete, then click on the `delete` button in the `layer controls`
   panel or press the delete key on your keyboard.
 
 * **Adding points**
-  ![image: Add points tool](../../images/point-adding-tool.png)
+  ![image: Add points tool](../../_static/images/point-adding-tool.png)
 
   New points can be added using the point adding tool, shown above, from the
   layer controls panel. Points can then be added by clicking in the canvas.
@@ -102,7 +102,7 @@ layer:
   select all points in a layer and the *deselect* points from a slice.
 
 * **Selecting points**
-  ![image: Select points tool](../../images/point-selecting-tool.png)
+  ![image: Select points tool](../../_static/images/point-selecting-tool.png)
 
   Select a point using the tool (shown above) and then clicking on that point.
   You can select multiple points by continuing to shift+click on additional
@@ -117,7 +117,7 @@ layer:
   to move around the `points` layer as you create your selection.
 
 * **Pan/zoom**
-  ![image: Pan/zoom tool](../../images/pan-zoom-tool.png)
+  ![image: Pan/zoom tool](../../_static/images/pan-zoom-tool.png)
 
   The default mode of the points layer supports panning and zooming, as in the
   image layer. This mode is represented by the magnifying glass in the layers
@@ -127,7 +127,7 @@ layer:
   pan and zoom mode by pressing the `4` key when the points layer is selected.
 
 * **Transform**
-  ![image: Transform](../../images/transform-tool.png)
+  ![image: Transform](../../_static/images/transform-tool.png)
 
   Use this tool to rotate, scale, or translate the layer. 
   Note: at present this feature is limited to 2D viewer display mode. To reset the transformation,
@@ -197,8 +197,8 @@ layer:
 
   All layers can be rendered in both 2D and 3D. The `Toggle ndisplay` button at
   the bottom of the left panel toggles between these 2 modes.
-  When in 2D, the button looks like this: ![image: 2D/3D button](../../images/3D-button.png), ready to switch to 3D mode.
-  When in 3D, the button looks like this: ![image: 2D/3D button](../../images/2D-button.png), ready to switch to 2D mode.
+  When in 2D, the button looks like this: ![image: 2D/3D button](../../_static/images/3D-button.png), ready to switch to 3D mode.
+  When in 3D, the button looks like this: ![image: 2D/3D button](../../_static/images/2D-button.png), ready to switch to 2D mode.
   You can also switch modes by pressing `Ctrl+y`.
 
   Note that when entering 3D rendering mode the GUI `Add point`,
diff --git a/docs/howtos/layers/shapes.md b/docs/howtos/layers/shapes.md
index f995a36b7..d80f18478 100644
--- a/docs/howtos/layers/shapes.md
+++ b/docs/howtos/layers/shapes.md
@@ -11,6 +11,7 @@ kernelspec:
   name: python3
 ---
 
+(layers-shapes)=
 # Using the `shapes` layer
 
 In this document, you will learn about the `napari` `shapes` layer, including
@@ -141,24 +142,24 @@ are used. i.e. You can't remove a vertex before you have created a shape.
 ### Buttons
 
 * **Remove vertex**
-  ![image: Remove vertex](../../images/shape_vertex_delete.png)
+  ![image: Remove vertex](../../_static/images/shape_vertex_delete.png)
 
   To remove a vertex, click this button and then click the vertex you want to
   remove.
 
 * **Insert vertex (Add vertex)**
-  ![image: Insert vertex](../../images/shape-vertex-insert.png)
+  ![image: Insert vertex](../../_static/images/shape-vertex-insert.png)
 
   Click this button and then click where you want to insert (add) a vertex.
 
 * **Delete selected shape**
-  ![image: Delete shape](../../images/shape-delete-shape.png)
+  ![image: Delete shape](../../_static/images/shape-delete-shape.png)
 
   Select the vertex to delete using the `select vertices` tool (below), then
   click this button, or hit the delete key on your keyboard.
 
 * **Select vertices**
-  ![image: Select vertices](../../images/shape-vertices-select.png)
+  ![image: Select vertices](../../_static/images/shape-vertices-select.png)
 
   Use this tool to select the vertex or vertices you want to move or delete. To
   select more than one vertex, select one, hold down the shift key and select
@@ -166,13 +167,13 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   location.
 
 * **Select shapes**
-  ![image: Select shapes](../../images/shape-select-shape.png)
+  ![image: Select shapes](../../_static/images/shape-select-shape.png)
 
   Use this tool to select the shape or shapes you want to delete. To select more
   than one shape, select one, hold down the shift key and select the rest.
 
 * **Pan/zoom**
-  ![image: Pan/zoom](../../images/pan-zoom-tool.png)
+  ![image: Pan/zoom](../../_static/images/pan-zoom-tool.png)
 
   Use this tool to pan around the layer or zoom in. Pan functionality
   is disabled when using the adding and editing tools; however, zoom using the mouse-wheel will typically continue to work. To activate the tool,
@@ -181,26 +182,26 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   layer as you edit it.
 
 * **Transform**
-  ![image: Transform](../../images/transform-tool.png)
+  ![image: Transform](../../_static/images/transform-tool.png)
 
   Use this tool to rotate, scale, or translate the layer. Note: at present this feature is limited to 2D viewer display mode. To activate the tool,
   you can press `7`. To reset the transformation, you can Option/Alt-click the
   transform button (a confirmation dialog will open to confirm the reset).
 
 * **Move to back**
-  ![image: Move to back](../../images/shape-move-to-back.png)
+  ![image: Move to back](../../_static/images/shape-move-to-back.png)
 
   Using the `select shapes` tool, select the shape to move behind other shapes
   and then click this button.
 
 * **Move to front**
-  ![image: Move to front](../../images/shape-move-to-front.png)
+  ![image: Move to front](../../_static/images/shape-move-to-front.png)
 
   Using the `select shapes` tool, select the shape to move in front of other
   shapes and then click this button.
 
 * **Add ellipses**
-  ![image: Add ellipses](../../images/shape-add-ellipses.png)
+  ![image: Add ellipses](../../_static/images/shape-add-ellipses.png)
 
   Use this tool to draw ovals or circles. Click the tool or press `e` (the
   default keybinding for this tool); next, click the point where you want the
@@ -210,7 +211,7 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   on that click.
 
 * **Add rectangles**
-  ![image: Add rectangles](../../images/shape-add-rectangles.png)
+  ![image: Add rectangles](../../_static/images/shape-add-rectangles.png)
 
   Select `Add rectangles` from the layer controls panel or by pressing the `r`
   key when the `shapes` layer is selected. Click and drag the rectangle to the
@@ -219,7 +220,7 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   centered on that click.
  
 * **Add polygons**
-  ![image: Add polygons](../../images/shape-add-polygons.png)
+  ![image: Add polygons](../../_static/images/shape-add-polygons.png)
 
   The `Add polygon` tool can be selected from the layer controls panel or by
   pressing the `p` key when the shapes layer is selected. When adding a polygon,
@@ -228,7 +229,7 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   position and completes the polygon. You can then add another polygon.
 
 * **Add polygons lasso**
-  ![image: Add polygons lasso](../../images/shape-add-lasso.png)
+  ![image: Add polygons lasso](../../_static/images/shape-add-lasso.png)
 
   `Polygons` can also be created with the polygon lasso creation tool, which can
   be found in the layer control panel or by pressing `shift+p`. The tool can be
@@ -273,7 +274,7 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   :::
 
 * **Add lines**
-  ![image: Add lines](../../images/shape-add-lines.png)
+  ![image: Add lines](../../_static/images/shape-add-lines.png)
 
   Select the `Add lines` tool from the layer controls panel or by pressing the
   `l` key when the shapes layer is selected. `Lines` consist of two vertices
@@ -283,7 +284,7 @@ are used. i.e. You can't remove a vertex before you have created a shape.
   of the second endpoint. Add other lines as needed.
 
 * **Add path**
-  ![image: Add path](../../images/shape-add-path.png)
+  ![image: Add path](../../_static/images/shape-add-path.png)
 
   Select the `Add path` tool from the layer controls panel or by pressing the
   `t` key when the shapes layer is selected. Click where you want the path to
@@ -331,8 +332,8 @@ are used. i.e. You can't remove a vertex before you have created a shape.
 
   All layers can be rendered in both 2D and 3D. The `Toggle ndisplay` button at
   the bottom of the left panel toggles between these 2 modes.
-  When in 2D, the button looks like this: ![image: 2D/3D button](../../images/3D-button.png), ready to switch to 3D mode.
-  When in 3D, the button looks like this: ![image: 2D/3D button](../../images/2D-button.png), ready to switch to 2D mode.
+  When in 2D, the button looks like this: ![image: 2D/3D button](../../_static/images/3D-button.png), ready to switch to 3D mode.
+  When in 3D, the button looks like this: ![image: 2D/3D button](../../_static/images/2D-button.png), ready to switch to 2D mode.
 
   You can also switch modes by pressing `ctrl+y`.
 
@@ -597,7 +598,7 @@ For paths that are defined by coordinates spanning more than two dimensions, it
 is possible to visualize them as 3D cylinders, see [](../../gallery/3D_paths)
 for examples.
 
-![image: 3D paths](../../images/3D_paths.png)
+![image: 3D paths](../../_static/images/3D_paths.png)
 
 ```{note}
 Right now, it is not possible to display 3D cuboids or 3D spheroids, but we will
diff --git a/docs/howtos/layers/surface.md b/docs/howtos/layers/surface.md
index 058f7c70a..8023adb44 100644
--- a/docs/howtos/layers/surface.md
+++ b/docs/howtos/layers/surface.md
@@ -11,6 +11,7 @@ kernelspec:
   name: python3
 ---
 
+(layers-surface)=
 # Using the `surface` layer
 
 In this document, you will learn about the `napari` `surface` layer, including
@@ -78,10 +79,10 @@ Once you have created a `surface` layer programmatically, the following GUI
 controls are available in the viewer:
 
 * **Buttons**
-  * Pan/zoom - ![image: Pan/zoom tool](../../images/pan-zoom-tool.png) is the default
+  * Pan/zoom - ![image: Pan/zoom tool](../../_static/images/pan-zoom-tool.png) is the default
     mode of the layer and supports panning and zooming. Press the `1` key when the
     layer is selected to use this mode.
-  * Transform - ![image: Transform](../../images/transform-tool.png) enables you to
+  * Transform - ![image: Transform](../../_static/images/transform-tool.png) enables you to
     rotate, scale, or translate the layer. Note: at present this feature is limited to 2D viewer display mode. To reset the transformation, you can
     Option/Alt-click the transform button (a confirmation dialog will open to
     confirm the reset). Press the `2` key when the layer is selected to use this mode.
@@ -125,8 +126,8 @@ list of values to associate with each vertex to use alongside a colormap. This
 
 All layers can be rendered in both 2D and 3D. One of the viewer buttons at the
 bottom of the left panel can toggle between these 2 modes.
-When in 2D, the button looks like this: ![image: 2D/3D button](../../images/3D-button.png), ready to switch to 3D mode.
-When in 3D, the button looks like this: ![image: 2D/3D button](../../images/2D-button.png), ready to switch to 2D mode.
+When in 2D, the button looks like this: ![image: 2D/3D button](../../_static/images/3D-button.png), ready to switch to 3D mode.
+When in 3D, the button looks like this: ![image: 2D/3D button](../../_static/images/2D-button.png), ready to switch to 2D mode.
 
 The number of dimensions sliders will be 2 or 3 less than the total number of
 dimensions of the layer, allowing you to browse volumetric timeseries data and
@@ -164,7 +165,7 @@ object. You can list all the available colormaps using `layer.colormaps`.
 It is also possible to create your own colormaps using vispy's
 `vispy.color.Colormap` object, see it's full
 [documentation here](https://vispy.org/api/vispy.color.colormap.html#vispy.color.colormap.Colormap).
-For more detail see the [image layer guide](image-layer).
+For more detail see the [image layer guide](layers-image).
 
 ## Adjusting contrast limits
 
@@ -172,5 +173,5 @@ The vertex values of the `surface` layer get mapped through its colormap accordi
 to values called `contrast limits`. These are a 2-tuple of values defining how
 what values get applied the minimum and maximum of the colormap and follow the
 same principles as the `contrast_limits` described in the
-[image layer guide](image-layer). They are also accessible through the same keyword
+[image layer guide](layers-image). They are also accessible through the same keyword
 arguments, properties, and GUI layer controls as in the image layer.
diff --git a/docs/howtos/layers/tracks.md b/docs/howtos/layers/tracks.md
index 3045a9ad9..80d05c264 100644
--- a/docs/howtos/layers/tracks.md
+++ b/docs/howtos/layers/tracks.md
@@ -12,7 +12,6 @@ kernelspec:
 ---
 
 (layers-tracks)=
-
 # Using the `tracks` layer
 
 In this document, you will learn about the `napari` `tracks` layer, including
@@ -93,10 +92,10 @@ napari.run()
 ## GUI controls for the `tracks` layer
 
 * **Buttons**
-  * Pan/zoom - ![image: Pan/zoom tool](../../images/pan-zoom-tool.png) is the default
+  * Pan/zoom - ![image: Pan/zoom tool](../../_static/images/pan-zoom-tool.png) is the default
     mode of the layer and supports panning and zooming. Press the `1` key when the
     layer is selected to use this mode.
-  * Transform - ![image: Transform](../../images/transform-tool.png) enables you to
+  * Transform - ![image: Transform](../../_static/images/transform-tool.png) enables you to
     rotate, scale, or translate the layer. Note: at present this feature is limited to 2D viewer display mode. To reset the transformation, you can
     Option/Alt-click the transform button (a confirmation dialog will open to
     confirm the reset). Press the `2` key when the layer is selected to use this mode.
@@ -211,8 +210,8 @@ properties of the tracks (e.g., the track color).
 
 All layers can be rendered in both 2D and 3D. One of the viewer buttons at the
 bottom of the left panel can toggle between these 2 modes.
-When in 2D, the button looks like this: ![image: 2D/3D button](../../images/3D-button.png), ready to switch to 3D mode.
-When in 3D, the button looks like this: ![image: 2D/3D button](../../images/2D-button.png), ready to switch to 2D mode.
+When in 2D, the button looks like this: ![image: 2D/3D button](../../_static/images/3D-button.png), ready to switch to 3D mode.
+When in 3D, the button looks like this: ![image: 2D/3D button](../../_static/images/2D-button.png), ready to switch to 2D mode.
 
 The number of dimensions sliders will be 2 or 3 less than the total number of
 dimensions of the layer, allowing you to browse volumetric timeseries data and
diff --git a/docs/howtos/layers/vectors.md b/docs/howtos/layers/vectors.md
index e4c6a781d..d4c4c20eb 100644
--- a/docs/howtos/layers/vectors.md
+++ b/docs/howtos/layers/vectors.md
@@ -11,6 +11,7 @@ kernelspec:
   name: python3
 ---
 
+(layers-vectors)=
 # Using the `vectors` layer
 
 In this document, you will learn about the `napari` `vectors` layer, including
@@ -86,10 +87,10 @@ Please refer to [A simple example](#a-simple-example) to add a `vectors` layer
 first, then explore the editing options the GUI provides.
 
 * **Buttons**
-  * Pan/zoom - ![image: Pan/zoom tool](../../images/pan-zoom-tool.png) is the default
+  * Pan/zoom - ![image: Pan/zoom tool](../../_static/images/pan-zoom-tool.png) is the default
     mode of the layer and supports panning and zooming. Press the `1` key when the
     layer is selected to use this mode.
-  * Transform - ![image: Transform](../../images/transform-tool.png) enables you to
+  * Transform - ![image: Transform](../../_static/images/transform-tool.png) enables you to
     rotate, scale, or translate the layer. Note: at present this feature is limited to 2D viewer display mode. To reset the transformation, you can
     Option/Alt-click the transform button (a confirmation dialog will open to
     confirm the reset). Press the `2` key when the layer is selected to use this mode.
@@ -128,8 +129,8 @@ you should use the `Lines` shape inside a `shapes` layer.
 
 All layers can be rendered in both 2D and 3D. One of the viewer buttons at the
 bottom of the left panel can toggle between these 2 modes.
-When in 2D, the button looks like this: ![image: 2D/3D button](../../images/3D-button.png), ready to switch to 3D mode.
-When in 3D, the button looks like this: ![image: 2D/3D button](../../images/2D-button.png), ready to switch to 2D mode.
+When in 2D, the button looks like this: ![image: 2D/3D button](../../_static/images/3D-button.png), ready to switch to 3D mode.
+When in 3D, the button looks like this: ![image: 2D/3D button](../../_static/images/2D-button.png), ready to switch to 2D mode.
 
 The number of dimensions sliders will be 2 or 3 less than the total number of
 dimensions of the layer, allowing you to browse volumetric timeseries data and
@@ -183,7 +184,7 @@ you have one vector per grid.
 Here is an example from [](../../gallery/add_vectors_image) of a grid of vectors
 defined over a random image:
 
-![image: add vectors overlaid on an image](../../images/add_vectors_image.png)
+![image: add vectors overlaid on an image](../../_static/images/add_vectors_image.png)
 
 Regardless of how the data is passed, we convert it to the `Nx2xD`
 representation internally. This representation is accessible through the
diff --git a/docs/images/3D-button.png b/docs/images/3D-button.png
deleted file mode 100644
index 155dfbbcc..000000000
Binary files a/docs/images/3D-button.png and /dev/null differ
diff --git a/docs/images/image_sc_logo.png b/docs/images/image_sc_logo.png
new file mode 100644
index 000000000..15fd3c3a8
Binary files /dev/null and b/docs/images/image_sc_logo.png differ
diff --git a/docs/images/mastodon_logo.svg b/docs/images/mastodon_logo.svg
new file mode 100644
index 000000000..a5a8d5397
--- /dev/null
+++ b/docs/images/mastodon_logo.svg
@@ -0,0 +1,10 @@
+<svg width="24" height="25" viewBox="0 0 75 79" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M73.8393 17.4898C72.6973 9.00165 65.2994 2.31235 56.5296 1.01614C55.05 0.797115 49.4441 0 36.4582 0H36.3612C23.3717 0 20.585 0.797115 19.1054 1.01614C10.5798 2.27644 2.79399 8.28712 0.904997 16.8758C-0.00358524 21.1056 -0.100549 25.7949 0.0682394 30.0965C0.308852 36.2651 0.355538 42.423 0.91577 48.5665C1.30307 52.6474 1.97872 56.6957 2.93763 60.6812C4.73325 68.042 12.0019 74.1676 19.1233 76.6666C26.7478 79.2728 34.9474 79.7055 42.8039 77.9162C43.6682 77.7151 44.5217 77.4817 45.3645 77.216C47.275 76.6092 49.5123 75.9305 51.1571 74.7385C51.1797 74.7217 51.1982 74.7001 51.2112 74.6753C51.2243 74.6504 51.2316 74.6229 51.2325 74.5948V68.6416C51.2321 68.6154 51.2259 68.5896 51.2142 68.5661C51.2025 68.5426 51.1858 68.522 51.1651 68.5058C51.1444 68.4896 51.1204 68.4783 51.0948 68.4726C51.0692 68.4669 51.0426 68.467 51.0171 68.4729C45.9835 69.675 40.8254 70.2777 35.6502 70.2682C26.7439 70.2682 24.3486 66.042 23.6626 64.2826C23.1113 62.762 22.7612 61.1759 22.6212 59.5646C22.6197 59.5375 22.6247 59.5105 22.6357 59.4857C22.6466 59.4609 22.6633 59.4391 22.6843 59.422C22.7053 59.4048 22.73 59.3929 22.7565 59.3871C22.783 59.3813 22.8104 59.3818 22.8367 59.3886C27.7864 60.5826 32.8604 61.1853 37.9522 61.1839C39.1768 61.1839 40.3978 61.1839 41.6224 61.1516C46.7435 61.008 52.1411 60.7459 57.1796 59.7621C57.3053 59.7369 57.431 59.7154 57.5387 59.6831C65.4861 58.157 73.0493 53.3672 73.8178 41.2381C73.8465 40.7606 73.9184 36.2364 73.9184 35.7409C73.9219 34.0569 74.4606 23.7949 73.8393 17.4898Z" fill="url(#paint0_linear_549_34)"/>
+<path d="M61.2484 27.0263V48.114H52.8916V27.6475C52.8916 23.3388 51.096 21.1413 47.4437 21.1413C43.4287 21.1413 41.4177 23.7409 41.4177 28.8755V40.0782H33.1111V28.8755C33.1111 23.7409 31.0965 21.1413 27.0815 21.1413C23.4507 21.1413 21.6371 23.3388 21.6371 27.6475V48.114H13.2839V27.0263C13.2839 22.7176 14.384 19.2946 16.5843 16.7572C18.8539 14.2258 21.8311 12.926 25.5264 12.926C29.8036 12.926 33.0357 14.5705 35.1905 17.8559L37.2698 21.346L39.3527 17.8559C41.5074 14.5705 44.7395 12.926 49.0095 12.926C52.7013 12.926 55.6784 14.2258 57.9553 16.7572C60.1531 19.2922 61.2508 22.7152 61.2484 27.0263Z" fill="white"/>
+<defs>
+<linearGradient id="paint0_linear_549_34" x1="37.0692" y1="0" x2="37.0692" y2="79" gradientUnits="userSpaceOnUse">
+<stop stop-color="#6364FF"/>
+<stop offset="1" stop-color="#563ACC"/>
+</linearGradient>
+</defs>
+</svg>
diff --git a/docs/images/twitter_logo.svg b/docs/images/twitter_logo.svg
new file mode 100644
index 000000000..fb48985b1
--- /dev/null
+++ b/docs/images/twitter_logo.svg
@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 248 204" height="25">
+  <path fill="#1d9bf0" d="M221.95 51.29c.15 2.17.15 4.34.15 6.53 0 66.73-50.8 143.69-143.69 143.69v-.04c-27.44.04-54.31-7.82-77.41-22.64 3.99.48 8 .72 12.02.73 22.74.02 44.83-7.61 62.72-21.66-21.61-.41-40.56-14.5-47.18-35.07 7.57 1.46 15.37 1.16 22.8-.87-23.56-4.76-40.51-25.46-40.51-49.5v-.64c7.02 3.91 14.88 6.08 22.92 6.32C11.58 63.31 4.74 33.79 18.14 10.71c25.64 31.55 63.47 50.73 104.08 52.76-4.07-17.54 1.49-35.92 14.61-48.25 20.34-19.12 52.33-18.14 71.45 2.19 11.31-2.23 22.15-6.38 32.07-12.26-3.77 11.69-11.66 21.62-22.2 27.93 10.01-1.18 19.79-3.86 29-7.95-6.78 10.16-15.32 19.01-25.2 26.16z"/>
+</svg>
\ No newline at end of file
diff --git a/docs/index.md b/docs/index.md
index 87204600d..5592f71a3 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -103,7 +103,7 @@ Get started with napari.
 :link: community
 :link-type: ref
 
-Forums, web chat, video chat, and more! Join us!
+Forums, web chat, video chat, where to ask questions and more! Join us!
 :::
 
 :::{grid-item-card} Governance
@@ -121,3 +121,4 @@ napari is extensible! Find plugins, or develop your own!
 :::
 
 ::::
+
diff --git a/docs/naps/2-conda-based-packaging.md b/docs/naps/2-conda-based-packaging.md
index e96bb659f..06837b939 100644
--- a/docs/naps/2-conda-based-packaging.md
+++ b/docs/naps/2-conda-based-packaging.md
@@ -607,13 +607,13 @@ CC0+BY [^cc0by].
 
 [^napari-releases-json]: <https://api.github.com/repos/napari/napari/releases>
 
-[^mne-constructor]: <https://twitter.com/mne_news/status/1506212014993162247>
+[^mne-constructor]: <https://x.com/mne_news/status/1506212014993162247>
 
 [^appimage-crash]: <https://github.com/napari/napari/issues/3487>
 
 [^appimage-crash2]: <https://github.com/napari/napari/issues/3816>
 
-[^napari-packaging-docs]: <https://napari.org/stable/developers/packaging.html>
+[^napari-packaging-docs]: <napari-packaging>
 
 [^napari-hub-api]: https://api.napari-hub.org/plugins
 
@@ -625,7 +625,7 @@ CC0+BY [^cc0by].
 
 [^briefcase-python]: https://github.com/beeware?q=Python+support&type=all&language=&sort=
 
-[^pypi-parallelism-abi]: https://twitter.com/ralfgommers/status/1517410559972589569
+[^pypi-parallelism-abi]: https://x.com/ralfgommers/status/1517410559972589569
 
 [^release-guide]: https://napari.org/stable/developers/release.html
 
diff --git a/docs/naps/5-new-logo.md b/docs/naps/5-new-logo.md
index c18c2f10c..7d7894cf4 100644
--- a/docs/naps/5-new-logo.md
+++ b/docs/naps/5-new-logo.md
@@ -29,7 +29,7 @@ A few months later, Jeremy Freeman, then director of Computational Biology at
 CZI, and a bit of a design nerd, traced the island and gave us our current,
 stylised version of that image.
 
-![napari-logo-2](../images/logo.png)
+![napari-logo-2](../_static/images/logo.png)
 
 Being, the shape is very irregular — no one knows what it is — and the
 gradients, the border around the logo, and the slightly rounded corners on a
@@ -55,7 +55,7 @@ smaller again by $\phi$ than the smaller circle, and one larger again than the
 bigger circle. In this way, the island is defined by four circles of increasing
 radius, with each increase a factor of $\phi$:
 
-![napari-logo-3-with-guides](../images/napari-logo-3-with-guides.png)
+![napari-logo-3-with-guides](../_static/images/napari-logo-3-with-guides.png)
 
 Additionally, the background of the logo is a
 [squircle](https://www.johndcook.com/blog/2018/02/13/squircle-curvature/) of
@@ -73,11 +73,11 @@ background in biology would appreciate!
 
 Here is the proposed logo together with the old one:
 
-![napari-logo-comparison](../images/napari-logo-old-new.png)
+![napari-logo-comparison](../_static/images/napari-logo-old-new.png)
 
 The new logo at 100% scale:
 
-![napari-logo-3](../images/napari-logo-3.png)
+![napari-logo-3](../_static/images/napari-logo-3.png)
 
 ## Related Work
 
@@ -161,7 +161,7 @@ for the logo, regardless of where this NAP lands.
 It's been suggested that the squircle shape might make it harder to tile a
 laptop together with other stickers, or align the edges. However, I think the
 tiling issue is a red herring because a quick look at the [NumFOCUS sticker
-table](https://twitter.com/NumFOCUS/status/1547651122654916609) shows that most
+table](https://x.com/NumFOCUS/status/1547651122654916609) shows that most
 related projects have irregularly-shaped stickers anyway. Additionally, I think
 that the squircle provides both a long enough straight edge (almost 1/3 of each
 side is exactly straight) to align things, but the smooth curvature makes
diff --git a/docs/naps/8-telemetry.md b/docs/naps/8-telemetry.md
index f87db52ee..998230376 100644
--- a/docs/naps/8-telemetry.md
+++ b/docs/naps/8-telemetry.md
@@ -190,7 +190,7 @@ from npe2 import plugin_manager
 from napari.utils.info import _sys_name
 from napari.plugins.npe2api import plugin_summaries
 from napari.plugins.utils import normalized_name
-from napari._app_model import get_app
+from napari._app_model import get_app_model
 
 
 def get_computer_identifier():
@@ -353,7 +353,7 @@ def get_full_information():
     data_collector = DataSizeTypeCollector.get_collector(
         Path(appdirs.user_config_dir("napari")) / "data_size_info.json"
     )
-    # app_model = get_app() - there is a need to add a collection of data to app_model
+    # app_model = get_app_model() - there is a need to add a collection of data to app_model
     return {
         **middle_info,
         "data_size_info": data_collector.data,
diff --git a/docs/naps/9-multiple-canvases.md b/docs/naps/9-multiple-canvases.md
index 31726dbd0..5fbbe276b 100644
--- a/docs/naps/9-multiple-canvases.md
+++ b/docs/naps/9-multiple-canvases.md
@@ -33,11 +33,11 @@ Current napari architecture supports a single canvas (viewbox) per viewer (windo
 The ability to view n-D data from multiple perspectives (or different data from the *same* perspective -- for example side-by-side segmentations) is a common feature request, and has proved useful in many other tools for data exploration and analysis. Here is a sampling of issues requesting support and discussing potential implementations:
 
 * [#5348](https://github.com/napari/napari/issues/5348) Multicanvas viewer
-* [#2338](https:////github.com/napari/napari/issues/2338) Multicanvas API Thoughts
-* [#760](https:////github.com/napari/napari/issues/760) Linked multicanvas support
-* [#662](https:////github.com/napari/napari/issues/662) Linked 2D views
-* [#561](https:////github.com/napari/napari/issues/561) multicanvas grid display for layers in Napari
-* [#1478](https:////github.com/napari/napari/issues/1478) Orthogonal viewer plugin
+* [#2338](https://github.com/napari/napari/issues/2338) Multicanvas API Thoughts
+* [#760](https://github.com/napari/napari/issues/760) Linked multicanvas support
+* [#662](https://github.com/napari/napari/issues/662) Linked 2D views
+* [#561](https://github.com/napari/napari/issues/561) multicanvas grid display for layers in Napari
+* [#1478](https://github.com/napari/napari/issues/1478) Orthogonal viewer plugin
 
 Several plugins and examples have been created to address these limitations, for example:
 * [napari-3d-ortho-viewer](https://github.com/gatoniel/napari-3d-ortho-viewer/tree/main)
diff --git a/docs/plugins/advanced_topics/npe1.md b/docs/plugins/advanced_topics/npe1.md
index 21e0ed385..88c20f3fe 100644
--- a/docs/plugins/advanced_topics/npe1.md
+++ b/docs/plugins/advanced_topics/npe1.md
@@ -176,7 +176,7 @@ specification in the same module or class, without needing a separate entry poin
 
 Packages and modules installed in the same environment as `napari` may make
 themselves "discoverable" to napari using package metadata, as outlined in the
-[Python Packaging Authority guide](https://packaging.python.org/guides/creating-and-discovering-plugins/#using-package-metadata).
+[Python Packaging Authority guide](https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/#using-package-metadata).
 
 By providing an `entry_points` argument with the key `napari.plugin` to
 `setup()` in `setup.py`, plugins can register themselves for discovery.
diff --git a/docs/plugins/building_a_plugin/best_practices.md b/docs/plugins/building_a_plugin/best_practices.md
index eba625a9f..29482f0f9 100644
--- a/docs/plugins/building_a_plugin/best_practices.md
+++ b/docs/plugins/building_a_plugin/best_practices.md
@@ -92,7 +92,7 @@ will run into difficulties installing your plugin:
   There's no one right way, but more often than not, if a package uses C
   extensions, the `setup()` function in their `setup.py` file will use the
   [`ext_modules`
-  argument](https://docs.python.org/3/distutils/setupscript.html#describing-extension-modules).
+  argument](https://docs.python.org/3.11/distutils/setupscript.html#describing-extension-modules).
   (for example, [see here in
   pytorch](https://github.com/pytorch/pytorch/blob/master/setup.py#L914))
 
diff --git a/docs/plugins/building_a_plugin/debug_plugins.md b/docs/plugins/building_a_plugin/debug_plugins.md
index 9e7587f46..54af6814b 100644
--- a/docs/plugins/building_a_plugin/debug_plugins.md
+++ b/docs/plugins/building_a_plugin/debug_plugins.md
@@ -35,7 +35,7 @@ To quickly get started with debugging your plugin, you can do the following:
 4. Run the created napari launch script in debug mode. For example, in VSCode, you can do this by opening the script in the editor, [selecting your napari virtual environment as the python interpreter](https://code.visualstudio.com/docs/python/environments) and then clicking the `Run and Debug` button in the left hand toolbar, selecting `Python: File` as the run configuration.
 5. At a breakpoint or exception (in VSCode, tick the `Raised Exceptions` box in the bottom left under the `Breakpoints` menu to see exceptions) you can then step through the code, inspect variables, and see the state of the napari viewer and your plugin. When you are done done debugging hit the continue button and napari will resume normal execution. See the image below for an example of a napari plugin debugging session in VSCode paused on a breakpoint.
 
-![debugging_in_vscode](../../images/vs_code_debug.png)
+![debugging_in_vscode](../../_static/images/vs_code_debug.png)
 
 ## Debugging plugin start-up issues
 
diff --git a/docs/plugins/building_a_plugin/first_plugin.md b/docs/plugins/building_a_plugin/first_plugin.md
index 8d8fca172..a34fc85b9 100644
--- a/docs/plugins/building_a_plugin/first_plugin.md
+++ b/docs/plugins/building_a_plugin/first_plugin.md
@@ -302,7 +302,7 @@ Review the [Best Practices](best-practices) when developing plugins and,
 when you're ready to share your plugin, see [Testing and Publishing](plugin-test-deploy).
 
 [miniconda]: https://docs.conda.io/projects/conda/en/latest/user-guide/install/download.html
-[python_env]: https://docs.conda.io/projects/conda/en/latest/user-guide/getting-started.html#managing-python
+[python_env]: https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-python.html
 [editable_mode]: https://pip.pypa.io/en/stable/cli/pip_install/#editable-installs
 [napari_plugin_template]: https://github.com/napari/napari-plugin-template
 [entry_points]: https://packaging.python.org/en/latest/specifications/entry-points/
diff --git a/docs/plugins/building_a_plugin/guides.md b/docs/plugins/building_a_plugin/guides.md
index e0c8f1b22..888ae020d 100644
--- a/docs/plugins/building_a_plugin/guides.md
+++ b/docs/plugins/building_a_plugin/guides.md
@@ -7,7 +7,7 @@ an example implementation. For details on the type and meaning of each
 field in a specific contribution, See the
 [contributions reference](contributions-ref)
 
-
+(plugin-readers-guide)=
 ```{include} ../_npe2_readers_guide.md
 ```
 ----------------
diff --git a/docs/plugins/start_using_plugins/finding_and_installing_plugins.md b/docs/plugins/start_using_plugins/finding_and_installing_plugins.md
index ca9b39354..3ad27be9a 100644
--- a/docs/plugins/start_using_plugins/finding_and_installing_plugins.md
+++ b/docs/plugins/start_using_plugins/finding_and_installing_plugins.md
@@ -17,7 +17,7 @@ directly from within napari:
 Firstly, from the “Plugins” menu, select “Install/Uninstall Plugins...”.
 Then, in the plugin installer menu that opens, you can either:
 
-![napari viewer's Plugins menu with Install/Uninstall Plugins as the first item.](/images/plugin-menu.png)
+![napari viewer's Plugins menu with Install/Uninstall Plugins as the first item.](../../_static/images/plugin-menu.png)
 
 1. Install plugins from the list: you can scroll through the list of “Available Plugins”, or
    filter plugins using the text box at the top of the dialog. From the list,
@@ -33,7 +33,7 @@ Then, in the plugin installer menu that opens, you can either:
     the “Install” button next to the input bar. This method allows for more flexibility
     in the plugins you can install, but it is also a bit more advanced.
 
-   ![napari viewer's Plugin dialog. At the bottom of the dialog, there is a place to install by name, URL, or dropping in a file.](/images/plugin-install-dialog.png)
+   ![napari viewer's Plugin dialog. At the bottom of the dialog, there is a place to install by name, URL, or dropping in a file.](../../_static/images/plugin-install-dialog.png)
 
    ```{admonition} Example
    If you want to install `napari-svg` directly from the development branch on the [github repository](https://github.com/napari/napari-svg), enter `git+https://github.com/napari/napari-svg.git` in the text field.
diff --git a/docs/plugins/testing_and_publishing/deploy.md b/docs/plugins/testing_and_publishing/deploy.md
index fc9e56c0d..42aed9562 100644
--- a/docs/plugins/testing_and_publishing/deploy.md
+++ b/docs/plugins/testing_and_publishing/deploy.md
@@ -57,7 +57,7 @@ forum](https://forum.image.sc/tag/napari).
 
 [classifier]: https://pypi.org/classifiers/
 [pypi]: https://pypi.org/
-[pypi-upload]: https://packaging.python.org/tutorials/packaging-projects/#uploading-the-distribution-archives
+[pypi-upload]: https://packaging.python.org/en/latest/tutorials/packaging-projects/#uploading-the-distribution-archives
 [hubguide]: https://github.com/chanzuckerberg/napari-hub/blob/main/docs/customizing-plugin-listing.md
 [hub-guide-custom-viz]: https://github.com/chanzuckerberg/napari-hub/wiki/Customizing-your-plugin's-listing#visibility
 [autodeploy]: https://github.com/napari/napari-plugin-template#set-up-automatic-deployments
diff --git a/docs/plugins/testing_workshop_docs/3-readers-and-fixtures.md b/docs/plugins/testing_workshop_docs/3-readers-and-fixtures.md
index 17096ed6e..bfa6fb883 100644
--- a/docs/plugins/testing_workshop_docs/3-readers-and-fixtures.md
+++ b/docs/plugins/testing_workshop_docs/3-readers-and-fixtures.md
@@ -24,12 +24,12 @@ The example plugin and all the tests discussed in this lesson are available in [
 ## Introduction
 In this lesson, we discuss a napari plugin called [plugin_tests](https://github.com/DragaDoncila/plugin-tests/tree/main/src/plugin_tests), generated using the [napari plugin template](https://github.com/napari/napari-plugin-template), which has a reader and a widget. The reader is the template [NumPy `.npy` file](https://numpy.org/doc/stable/reference/generated/numpy.lib.format.html#npy-format) reader, `napari_get_reader`. It checks whether a path ends in `.npy`. If it doesn't, it returns `None`, and if it does, it returns the `reader_function`, which loads the data.
 
-![napari_get_reader](../../images/napari_plugins_1st_napari_get_reader.png)
+![napari_get_reader](../../_static/images/napari_plugins_1st_napari_get_reader.png)
 
 ## Reader
 The `napari_get_reader` function is the first thing to test. In the top-level directory under `src`, we have the `plugin_tests` module. Inside `plugin_tests` is the `_tests` directory. This is a typical structure when writing tests. There is also a `test_reader.py` file, which is empty. We will populate it with tests.
 
-![reader_function](../../images/napari_plugins_2nd_reader_function.png)
+![reader_function](../../_static/images/napari_plugins_2nd_reader_function.png)
 
 We are focused on testing the `napari_get_reader` function. Sometimes it returns `None`; sometimes it returns the `reader_function`. We want to ensure that if we pass in a path that ends with `.npy`, it gives us back a function we can call.  We import `numpy` and `napari_get_reader`. `numpy` will be used later.
 
@@ -64,7 +64,7 @@ def test_get_reader_returns_callable(tmp_path):
 
 Running the command `pytest .` in the root directory of the plugin, we discover all the functions recognized as tests. It should recognize `test_reader.py` because it's a test file, prefixed with the word test. `test_reader.py` was found and passed the test.
 
-![pytest passed](../../images/napari_plugins_3rd_pytest_passed.png)
+![pytest passed](../../_static/images/napari_plugins_3rd_pytest_passed.png)
 
 If the file did not end in `.npy` the test would fail because what was returned wasn't callable. This code has been modified to produce an error:
 ```python
@@ -83,7 +83,7 @@ def test_get_reader_returns_callable(tmp_path):
 ```
 Once we run `pytest` we can see that it traced back that the callable of `reader` is `False` and it has filled in the fact that `reader` at the time of the assertion was `None`. This is useful in debugging.
 
-![test_get_reader_returns_callable Failed](../../images/napari_plugins_4th_test_get_reader_returns_callable-failed.png)
+![test_get_reader_returns_callable Failed](../../_static/images/napari_plugins_4th_test_get_reader_returns_callable-failed.png)
 
 ## Custom fixtures and round-trip tests
 Next, we test to see if this function reads the data. This is a round-trip test. We will create a fixture to write the data to make things easier for ourselves. This fixture will be called [test_reader_round_trip](https://github.com/DragaDoncila/plugin-tests/blob/effb32d6e3b191ad83e69813b26ae8695210f5ad/src/plugin_tests/_tests/test_reader.py#L39).
@@ -96,7 +96,7 @@ We will have access to what `write_func` returns once it’s been called inside
 
 The benefit of creating this fixture is that whenever we want to write our own test data we don't have to copy three lines of code, we can just use the fixture. This is useful in testing data with different structures like integers or a specific layer type. Those arguments could be passed to further customize your fixture.
 
-We still want to make sure we get a reader when we call `napari_get_reader` with the file. We call that `reader` function with the file we created to see if it returns what we expect. Based on the [reader spec](https://napari.org/stable/plugins/contributions.html#contributions-readers), it should return a layer data list. Here is the full test, with the fixture:
+We still want to make sure we get a reader when we call `napari_get_reader` with the file. We call that `reader` function with the file we created to see if it returns what we expect. Based on the [reader spec](plugin-readers-guide), it should return a layer data list. Here is the full test, with the fixture:
 ```python
 @pytest.fixture
 def write_im_to_file(tmp_path):
@@ -144,7 +144,7 @@ def test_reader_round_trip(write_im_to_file):
 ```
 We run our tests again, and now two are collected, both passing.
 
-![pytest - tests passed](../../images/napari_plugins_5th_tests_passed.png)
+![pytest - tests passed](../../_static/images/napari_plugins_5th_tests_passed.png)
 
 
 ## Enclosed testing
diff --git a/docs/plugins/testing_workshop_docs/4-test-coverage.md b/docs/plugins/testing_workshop_docs/4-test-coverage.md
index dc0b9839d..c4728a458 100644
--- a/docs/plugins/testing_workshop_docs/4-test-coverage.md
+++ b/docs/plugins/testing_workshop_docs/4-test-coverage.md
@@ -66,13 +66,13 @@ There is a large folder (`htmlcov`) in the directory where the tests were run (`
 
 If we open the `index.html` file from the list of files in the left panel (to the left of line 32) in a browser, we can see the coverage report.
 
-![htmlcov directory](../../images/test_coverage_htmlcov_directory.png)
+![htmlcov directory](../../_static/images/test_coverage_htmlcov_directory.png)
 
-![Coverage Report](../../images/coverage_report.png)
+![Coverage Report](../../_static/images/coverage_report.png)
 
 We are interested in `_reader.py`. The file containing the reader code has 86% coverage (see below). Clicking ok on the `2 missing` box below highlights the lines that were never run at all. They are highlighted in red (lines 22 and 26):
 
-![Lines not run highlighted in red](../../images/lines_not_run_highlighted_in_red.png)
+![Lines not run highlighted in red](../../_static/images/lines_not_run_highlighted_in_red.png)
 
 Because we never provided a list of paths, we don't know what will happen in that case. We also never ran code that tests not returning a reader. In other words, we never tested the failed cases. We can and should add those tests. The first one is `test_get_reader_pass`. We'll call it with a file that doesn't end in `.npy` and assert that it returned `None`. Then we'll create a second test to call with a list of paths.
 
@@ -96,7 +96,7 @@ If we re-run `pytest`, the coverage report is also updated and coverage should i
 
 The coverage report goes to the same folder, `htmlcov`, so we should be able to refresh the page without opening the file again. We've now got 100% coverage of `_reader.py` now. See below.
 
-![second coverage report](../../images/second_coverage_report.png)
+![second coverage report](../../_static/images/second_coverage_report.png)
 
 There could be other, more complicated cases that we have not tested, but at the very least, we are executing all lines of code.
 
diff --git a/docs/plugins/testing_workshop_docs/testing-resources.md b/docs/plugins/testing_workshop_docs/testing-resources.md
index c3f0301f6..5d2872307 100644
--- a/docs/plugins/testing_workshop_docs/testing-resources.md
+++ b/docs/plugins/testing_workshop_docs/testing-resources.md
@@ -14,6 +14,6 @@ Important: Instances of this class should be accessed only by using a qtbot fixt
 
 * [codecov](https://about.codecov.io/) - As long as your code has tests and your coverage tool can output coverage results you can use Codecov.
 
-* [GitHub workflow docs](https://docs.github.com/en/actions/quickstart) - You need only a GitHub repository to create and run a GitHub Actions workflow.
+* [GitHub workflow docs](https://docs.github.com/en/actions/writing-workflows/quickstart) - You need only a GitHub repository to create and run a GitHub Actions workflow.
 
-* [Slides from workshop presentation](https://docs.google.com/presentation/d/1RFja0o6cZ8lAalAve8heuJ-Lrb4nOSUnfdpOSEhqqNo/) - These are the actual slides that were used during the testing workshop.
\ No newline at end of file
+* [Slides from workshop presentation](https://docs.google.com/presentation/d/1RFja0o6cZ8lAalAve8heuJ-Lrb4nOSUnfdpOSEhqqNo) - These are the actual slides that were used during the testing workshop.
diff --git a/docs/plugins/virtual_environment_docs/2-deploying-your-plugin.md b/docs/plugins/virtual_environment_docs/2-deploying-your-plugin.md
index 6109909b0..1ae82f2ff 100644
--- a/docs/plugins/virtual_environment_docs/2-deploying-your-plugin.md
+++ b/docs/plugins/virtual_environment_docs/2-deploying-your-plugin.md
@@ -90,7 +90,7 @@ jobs:
 
 ```
 
-  **Note:** Gate this action on some criterion, e.g. a git tag as above, or [some other criterion](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows).
+  **Note:** Gate this action on some criterion, e.g. a git tag as above, or [some other criterion](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows).
 
 (deploying-to-anaconda)=
 ## Deploying to Anaconda
diff --git a/docs/plugins/virtual_environment_docs/4-developer-tools.md b/docs/plugins/virtual_environment_docs/4-developer-tools.md
index 620949e8d..82d67a8ca 100644
--- a/docs/plugins/virtual_environment_docs/4-developer-tools.md
+++ b/docs/plugins/virtual_environment_docs/4-developer-tools.md
@@ -25,7 +25,7 @@ These _check_ your code.
 These _auto-modify_ your code.
 * [black](https://github.com/psf/black)
   Forces code to follow specific style, indentations, etc...
-* [autoflake](https://github.com/myint/autoflake)
+* [autoflake](https://github.com/PyCQA/autoflake)
   Auto-fixes some flake8 failures.
 * [isort](https://github.com/PyCQA/isort)
   Auto-sorts and formats your imports.
diff --git a/docs/plugins/virtual_environment_docs/5-survey.md b/docs/plugins/virtual_environment_docs/5-survey.md
index 8248efdb6..1f580a11f 100644
--- a/docs/plugins/virtual_environment_docs/5-survey.md
+++ b/docs/plugins/virtual_environment_docs/5-survey.md
@@ -36,7 +36,7 @@ Answer:
 Question: How can we find the different signals/slots we can connect callbacks to as the user interacts with the core napari interface e.g. creating/editing/deleting a `points` or `shapes` layer?
 
 Answer:
-[https://napari.org/guides/stable/events_reference.html](https://napari.org/stable/guides/events_reference.html)
+[Events reference](events-reference)
 
 Granted, this is a work in progress.
 
@@ -61,7 +61,7 @@ Question: How do you make a process cancellable to interrupt a method that is ru
 
 Answer:
 * In single-threaded python, use `Ctrl-C`
-* In multithreaded python, there are many different patterns. Consider using a [generator-based thread worker](https://napari.org/stable/guides/threading.html#generators-for-the-win).
+* In multithreaded python, there are many different patterns. Consider using a [generator-based thread worker](generators-for-the-win).
 
 ## Are there testing environments in napari?
 Answer: Napari does not create or otherwise manage environments.
@@ -71,12 +71,12 @@ Answer:
 * The primary difference is in how plugins are discovered:
     - npe1 used decorators, requiring module import.
     - npe2 uses static manifests (`napari.yaml`), describing contributions without requiring import.
-    - See also the [Your First Plugin tutorial](https://napari.org/stable/plugins/first_plugin.html)
+    - See also the [Your First Plugin tutorial](your-first-plugin)
 
 Additional resources:
-* [Contributions Reference](https://napari.org/stable/plugins/contributions.html)
-* [Guides for each type of contribution](https://napari.org/stable/plugins/guides.html)
-* [Migration guide](https://napari.org/stable/plugins/npe2_migration_guide.html)
+* [Contributions Reference](contributions-ref)
+* [Guides for each type of contribution](plugin-contribution-guides)
+* [Migration guide](npe2-migration-guide)
 
 ## What is the optimal setup to quickly iterate in widget development?
 Answer:
diff --git a/docs/release/generate_release_notes.py b/docs/release/generate_release_notes.py
deleted file mode 100644
index df89f5e78..000000000
--- a/docs/release/generate_release_notes.py
+++ /dev/null
@@ -1,351 +0,0 @@
-"""Generate the release notes automatically from Github pull requests.
-Start with:
-```
-export GH_TOKEN=<your-gh-api-token>
-```
-Then, for to include everything from a certain release to main:
-```
-python /path/to/generate_release_notes.py v0.14.0 main --version 0.15.0
-```
-Or two include only things between two releases:
-```
-python /path/to/generate_release_notes.py v.14.2 v0.14.3 --version 0.14.3
-```
-You should probably redirect the output with:
-```
-python /path/to/generate_release_notes.py [args] | tee release_notes.md
-```
-You'll require PyGitHub and tqdm, which you can install with:
-```
-python -m pip install -e ".[release]"
-```
-References
-https://github.com/scikit-image/scikit-image/blob/main/tools/generate_release_notes.py
-https://github.com/scikit-image/scikit-image/issues/3404
-https://github.com/scikit-image/scikit-image/issues/3405
-"""
-import argparse
-import os
-import re
-import sys
-from collections import OrderedDict
-from contextlib import contextmanager
-from datetime import datetime
-from itertools import chain
-from os.path import abspath
-from pathlib import Path
-from warnings import warn
-
-from git import Repo
-from github import Github
-
-try:
-    import requests
-    import requests_cache
-
-    requests_cache.install_cache(
-        'github_cache', backend='sqlite', expire_after=3600
-    )
-    # setup cache for speedup execution and reduce number of requests to GitHub API
-    # cache will expire after 1h (3600s)
-
-    @contextmanager
-    def short_cache(new_time):
-        if requests_cache.get_cache() is None:
-            yield
-            return
-        session = requests.Session()
-        old_time = session.expire_after
-        session.expire_after = new_time
-        try:
-            yield
-        finally:
-            session.expire_after = old_time
-
-except ImportError:
-
-    @contextmanager
-    def short_cache(new_time):
-        """dummy context manager"""
-        yield
-
-
-try:
-    from tqdm import tqdm
-except ModuleNotFoundError:
-    warn(
-        'tqdm not installed. This script takes approximately 5 minutes '
-        'to run. To view live progressbars, please install tqdm. '
-        'Otherwise, be patient.'
-    )
-
-    def tqdm(i, **kwargs):
-        return i
-
-
-pr_num_pattern = re.compile(r'\(#(\d+)\)(?:$|\n)')
-issue_pattern = re.compile(
-    r'(?:Close|Closes|close|closes|Fix|Fixes|fix|fixes|Resolves|resolves) +#(\d+)'
-)
-
-GH = "https://github.com"
-GH_USER = 'napari'
-GH_REPO = 'napari'
-GH_TOKEN = os.environ.get('GH_TOKEN')
-if GH_TOKEN is None:
-    raise RuntimeError(
-        "It is necessary that the environment variable `GH_TOKEN` "
-        "be set to avoid running into problems with rate limiting. "
-        "One can be acquired at https://github.com/settings/tokens.\n\n"
-        "You do not need to select any permission boxes while generating "
-        "the token."
-    )
-
-g = Github(GH_TOKEN)
-repository = g.get_repo(f'{GH_USER}/{GH_REPO}')
-
-local_repo = Repo(Path(abspath(__file__)).parent.parent.parent)
-
-
-parser = argparse.ArgumentParser(usage=__doc__)
-parser.add_argument('from_commit', help='The starting tag.')
-parser.add_argument('to_commit', help='The head branch.')
-parser.add_argument(
-    '--version', help="Version you're about to release.", default='0.2.0'
-)
-
-args = parser.parse_args()
-
-for tag in repository.get_tags():
-    if tag.name == args.from_commit:
-        previous_tag = tag
-        break
-else:
-    raise RuntimeError(f'Desired tag ({args.from_commit}) not found')
-
-common_ancestor = local_repo.merge_base(args.to_commit, args.from_commit)[0]
-remote_commit = repository.get_commit(common_ancestor.hexsha)
-
-# For some reason, go get the github commit from the commit to get
-# the correct date
-previous_tag_date = datetime.strptime(
-    remote_commit.last_modified, '%a, %d %b %Y %H:%M:%S %Z'
-)
-
-
-def get_commits_to_ancestor(ancestor, rev="main"):
-    yield from local_repo.iter_commits(f'{ancestor.hexsha}..{rev}')
-
-
-new_commits_count = (
-    len(list(get_commits_to_ancestor(common_ancestor, args.to_commit))) + 1
-)
-release_branch_count = (
-    len(list(get_commits_to_ancestor(common_ancestor, args.from_commit))) + 1
-)
-
-with short_cache(60):
-    all_commits = list(
-        tqdm(
-            repository.get_commits(
-                sha=args.to_commit, since=previous_tag_date
-            ),
-            desc=f'Getting all commits between {remote_commit.sha} '
-            f'and {args.to_commit}',
-            total=new_commits_count,
-        )
-    )
-branch_commit = list(
-    tqdm(
-        repository.get_commits(
-            sha=local_repo.tag(args.from_commit).commit.hexsha,
-            since=previous_tag_date,
-        ),
-        desc=f'Getting all commits from release branch {args.from_commit} '
-        f'and {remote_commit.sha}',
-        total=release_branch_count,
-    )
-)
-all_hashes = {c.sha for c in all_commits}
-
-consumed_pr = set()
-
-for commit in branch_commit:
-    if match := pr_num_pattern.search(commit.commit.message):
-        consumed_pr.add(int(match[1]))
-
-
-def add_to_users(users, new_user):
-    if new_user.login in users:
-        # reduce obsolete requests to GitHub API
-        return
-    if new_user.name is None:
-        users[new_user.login] = new_user.login
-    else:
-        users[new_user.login] = new_user.name
-
-
-authors = set()
-committers = set()
-reviewers = set()
-users = {}
-
-for commit in tqdm(all_commits, desc="Getting committers and authors"):
-    if match := pr_num_pattern.search(commit.commit.message):
-        if int(match[1]) in consumed_pr:
-            continue
-            # omit commits from release branch
-
-    if commit.committer is not None:
-        add_to_users(users, commit.committer)
-        committers.add(commit.committer.login)
-    if commit.author is not None:
-        add_to_users(users, commit.author)
-        authors.add(commit.author.login)
-
-# remove these bots.
-committers.discard("web-flow")
-authors.discard("azure-pipelines-bot")
-
-highlights = OrderedDict()
-
-highlights['Highlights'] = {}
-highlights['New Features'] = {}
-highlights['Enhancements'] = {}
-highlights["Performance"] = {}
-highlights['Bug Fixes'] = {}
-highlights['API Changes'] = {}
-highlights['Deprecations'] = {}
-highlights['Maintenance'] = {}
-highlights['Dependencies'] = {}
-highlights['Documentation'] = {}
-other_pull_requests = {}
-
-label_to_section = {
-    "bugfix": "Bug Fixes",
-    "feature": "New Features",
-    "performance": "Performance",
-    "enhancement": "Enhancements",
-    "maintenance": "Maintenance",
-    "documentation": "Documentation",
-    # things in here could be duplicates of the above
-    "highlight": "Highlights",
-    "api": "API Changes",
-    "dependencies": "Dependencies",
-    "deprecation": "Deprecations",
-}
-
-pr_count = 0
-
-for commit in get_commits_to_ancestor(common_ancestor, args.to_commit):
-    if pr_num_pattern.search(commit.message) is not None:
-        pr_count += 1
-
-for pull in tqdm(
-    g.search_issues(
-        f'repo:{GH_USER}/{GH_REPO} '
-        f'merged:>{previous_tag_date.isoformat()} '
-        'sort:created-asc'
-    ),
-    desc='Pull Requests...',
-    total=pr_count,
-):
-    if pull.number in consumed_pr:
-        continue
-    if pull.milestone is not None and pull.milestone.title != args.version:
-        print(
-            f"PR {pull.number} is assigned to milestone {pull.milestone.title}",
-            file=sys.stderr,
-        )
-    pr = repository.get_pull(pull.number)
-    if pr.merge_commit_sha not in all_hashes:
-        continue
-    summary = pull.title
-
-    for review in pr.get_reviews():
-        if review.user is not None:
-            add_to_users(users, review.user)
-            reviewers.add(review.user.login)
-    assigned_to_section = False
-    pr_lables = {label.name.lower() for label in pull.labels}
-    for label_name, section in label_to_section.items():
-        if label_name in pr_lables:
-            highlights[section][pull.number] = {'summary': summary}
-            assigned_to_section = True
-
-    if assigned_to_section:
-        continue
-
-    issues_list = []
-    if pull.body:
-        for x in issue_pattern.findall(pull.body):
-            issue = repository.get_issue(int(x))
-            if issue.pull_request is None:
-                issues_list.append(issue)
-
-    issue_labels = [
-        label.name for label in chain(*[x.labels for x in issues_list])
-    ]
-
-    for label_name, section in label_to_section.items():
-        if label_name in issue_labels:
-            highlights[section][pull.number] = {'summary': summary}
-            break
-    else:
-        other_pull_requests[pull.number] = {'summary': summary}
-
-
-# add Other PRs to the ordered dict to make doc generation easier.
-highlights['Other Pull Requests'] = other_pull_requests
-
-
-# Now generate the release notes
-title = f'# napari {args.version}'
-print(title)
-
-print(
-    f"""
-We're happy to announce the release of napari {args.version}!
-napari is a fast, interactive, multi-dimensional image viewer for Python.
-It's designed for browsing, annotating, and analyzing large multi-dimensional
-images. It's built on top of Qt (for the GUI), vispy (for performant GPU-based
-rendering), and the scientific Python stack (numpy, scipy).
-"""
-)
-
-print(
-    """
-For more information, examples, and documentation, please visit our website:
-https://github.com/napari/napari
-"""
-)
-
-for section, pull_request_dicts in highlights.items():
-    print(f'## {section}\n')
-    for number, pull_request_info in pull_request_dicts.items():
-        print(f'- {pull_request_info["summary"]} (#{number})')
-    print()
-
-
-contributors = OrderedDict()
-
-contributors['authors'] = authors
-contributors['reviewers'] = reviewers
-# ignore committers
-# contributors['committers'] = committers
-
-for section_name, contributor_set in contributors.items():
-    print()
-    if None in contributor_set:
-        contributor_set.remove(None)
-    committer_str = (
-        f'## {len(contributor_set)} {section_name} added to this '
-        'release (alphabetical)'
-    )
-    print(committer_str)
-    print()
-
-    for c in sorted(contributor_set, key=lambda x: users[x].lower()):
-        commit_link = f"{GH}/{GH_USER}/{GH_REPO}/commits?author={c}"
-        print(f"- [{users[c]}]({commit_link}) - @{c}")
-    print()
diff --git a/docs/release/release_0_4_15.md b/docs/release/release_0_4_15.md
index 4131c0c31..0192d3d9e 100644
--- a/docs/release/release_0_4_15.md
+++ b/docs/release/release_0_4_15.md
@@ -37,7 +37,7 @@ If users install this third-party package, they will be presented with a
 dialog asking whether to opt-in to report errors to select napari core
 developers, which will help us prioritise and fix bugs that we might otherwise
 miss. See the project's
-[README](https://github.com/tlambert03/napari-error-reporter/#readme) for
+[README](https://github.com/tlambert03/napari-error-reporter/) for
 details.
 
 Finally, we have made some updates to how our application works. We now provide
diff --git a/docs/release/release_0_4_17.md b/docs/release/release_0_4_17.md
index 09756d95c..c2f90de9f 100644
--- a/docs/release/release_0_4_17.md
+++ b/docs/release/release_0_4_17.md
@@ -20,7 +20,7 @@ We picked out a few highlights, but keep reading below for the full list of chan
 We added a new blending mode, `minimum`, in #4875, along with some inverted colormaps by @cleterrier.
 The new mode and colormaps enable visualizing data as color intensities on a white background.
 This is particularly nice when using the Light theme.
-For more inspiration see [#invertedLUT on Twitter](https://twitter.com/hashtag/invertedLUT)
+For more inspiration see [#invertedLUT on Twitter](https://x.com/hashtag/invertedLUT)
 and the built-in napari example [examples/minimum_blending.py](https://github.com/napari/napari/blob/main/examples/minimum_blending.py).
 
 ### Option to edit second shortcut in preferences
diff --git a/docs/release/release_0_4_6.md b/docs/release/release_0_4_6.md
index 3733b2779..d5dd27f66 100644
--- a/docs/release/release_0_4_6.md
+++ b/docs/release/release_0_4_6.md
@@ -62,7 +62,7 @@ package name, url, or local file (#2319).
 
 ## API Changes
 - The ViewerModel is now a Pydantic BaseModel and so subclassing the Viewer might require
-reading some of the [Pydantic BaseModel documentation](https://pydantic-docs.helpmanual.io/usage/models/).
+reading some of the [Pydantic BaseModel documentation](https://docs.pydantic.dev/latest/usage/models/).
 Otherwise the API of the ViewerModel is unchanged.
 - Because `Labels` no longer inherit from `Image` (#2307), magicgui function
   parameters annotated as `napari.layers.Image` will no longer include
diff --git a/docs/release/release_0_5_0.md b/docs/release/release_0_5_0.md
index 8efe3e05e..ba83c898a 100644
--- a/docs/release/release_0_5_0.md
+++ b/docs/release/release_0_5_0.md
@@ -51,7 +51,7 @@ between layers ([#6864](https://github.com/napari/napari/pull/6864)).
 
 You'll also note a new little button on layer controls, including images:
 
-```{image} ../images/transform-icon.svg
+```{image} ../_static/images/transform-icon.svg
 :alt: transform layer icon
 :width: 100px
 :align: center
diff --git a/docs/release/release_0_5_2.md b/docs/release/release_0_5_2.md
new file mode 100644
index 000000000..2527f3cc1
--- /dev/null
+++ b/docs/release/release_0_5_2.md
@@ -0,0 +1,115 @@
+# napari 0.5.2
+
+*Tuesday, Aug 13, 2024*
+
+We’re happy to announce the release of napari 0.5.2!
+
+napari is a fast, interactive, multi-dimensional image viewer for Python. It’s designed for exploring, annotating, and analyzing multi-dimensional images. It’s built on Qt (for the GUI), VisPy (for performant GPU-based rendering), and the scientific Python stack (NumPy, SciPy, and friends).
+
+For more information, examples, and documentation, please visit our website: https://napari.org/
+
+## Highlights
+
+This is primarily a bug-fix release, but we snuck a couple of new features in
+there, including smoother, prettier, better rendering of Labels volumes in 3D
+([#7100](https://github.com/napari/napari/pull/7100)) and the ability to
+display scale bar at a fixed length in world coordinates, rather than having it
+resize dynamically to take up a small part of the screen
+([#7167](https://github.com/napari/napari/pull/7100)).
+
+See below for the full list of changes!
+
+## New Features
+
+- Add option for smoother labels rendering in 3D ([#7100](https://github.com/napari/napari/pull/7100))
+- Add optional fixed `length` parameter to scale bar  ([#7167](https://github.com/napari/napari/pull/7167))
+
+## Improvements
+
+- Update shortcuts.py to have `Enter` be primary Shapes completion ([#7063](https://github.com/napari/napari/pull/7063))
+- Change shortcuts `_mark_conflicts` logic to always compare between strings representations of shortcuts ([#7124](https://github.com/napari/napari/pull/7124))
+- Allow easy call single benchmark ([#7145](https://github.com/napari/napari/pull/7145))
+
+## Bug Fixes
+
+- [bugfix] update Point size slider on selection (current_size event) ([#7137](https://github.com/napari/napari/pull/7137))
+- Disconnect all dims events when closing viewer ([#7140](https://github.com/napari/napari/pull/7140))
+- Update event connection order ([#7150](https://github.com/napari/napari/pull/7150))
+- Run slider animation without using timer ([#7158](https://github.com/napari/napari/pull/7158))
+- Emit highlight event only if selection changed ([#7162](https://github.com/napari/napari/pull/7162))
+- [Bugfix] Only import darkdetect when needed ([#7163](https://github.com/napari/napari/pull/7163))
+- FIX `QtViewer._open_files_dialog` handing of `stack` ([#7172](https://github.com/napari/napari/pull/7172))
+
+## Documentation
+
+- Update example annotate_segmentation_with_text.py to add link to the tutorial ([#7134](https://github.com/napari/napari/pull/7134))
+- Document command ID naming conventions ([docs#405](https://github.com/napari/docs/pull/405))
+- Turn on warnings as error option for sphinx build ([docs#409](https://github.com/napari/docs/pull/409))
+- Update version switcher for v0.5.1 ([docs#468](https://github.com/napari/docs/pull/468))
+- Add documentation for run benchmark under debugger ([docs#470](https://github.com/napari/docs/pull/470))
+- Update installation notes about macOS arm processors and Qt5 backends  ([docs#471](https://github.com/napari/docs/pull/471))
+- Fix docs CI ([docs#472](https://github.com/napari/docs/pull/472))
+- Add October and July workshops from 2023 ([docs#473](https://github.com/napari/docs/pull/473))
+- Add 0.5.2 release notes ([docs#476](https://github.com/napari/docs/pull/476))
+- Remove warning and update date on 0.5.2 release notes ([docs#478](https://github.com/napari/docs/pull/478))
+
+## Other Pull Requests
+
+- [pre-commit.ci] pre-commit autoupdate ([#7000](https://github.com/napari/napari/pull/7000))
+- Add CI action to check that set milestone is the next release ([#7083](https://github.com/napari/napari/pull/7083))
+- Use app-model `KeyBinding.to_text` and `KeyCode.os_symbol` over `Shortcut` logic ([#7113](https://github.com/napari/napari/pull/7113))
+- Add some basic codeowners ([#7118](https://github.com/napari/napari/pull/7118))
+- Clean action manager to avoid side effects during tests ([#7120](https://github.com/napari/napari/pull/7120))
+- [maint] Drop singularity action to fix failed container action ([#7121](https://github.com/napari/napari/pull/7121))
+- Remove `post` identifier in fetching release notes ([#7125](https://github.com/napari/napari/pull/7125))
+- Update `coverage`, `hypothesis`, `magicgui`, `matplotlib`, `napari-plugin-manager`, `npe2`, `pytest`, `tensorstore`, `tifffile`, `tqdm`, `xarray` ([#7138](https://github.com/napari/napari/pull/7138))
+- ci(dependabot): bump the actions group across 1 directory with 2 updates ([#7147](https://github.com/napari/napari/pull/7147))
+- [Maint] Update version_denylist.txt to block mpl 3.9.1 on windows ([#7154](https://github.com/napari/napari/pull/7154))
+- [Maint] Increase timeout in `test_async_out_of_bounds_layer_loaded` to 500 ms ([#7157](https://github.com/napari/napari/pull/7157))
+- Use `delete` instead of `get`method for delete `ready to merge` label ([#7160](https://github.com/napari/napari/pull/7160))
+- [pre-commit.ci] pre-commit autoupdate ([#7161](https://github.com/napari/napari/pull/7161))
+- fix: typo in shape model name ([#7166](https://github.com/napari/napari/pull/7166))
+- Update `dask`, `hypothesis`, `magicgui`, `matplotlib`, `pyyaml` ([#7169](https://github.com/napari/napari/pull/7169))
+- Update docs constraints to pin sphinx<8 ([#7170](https://github.com/napari/napari/pull/7170))
+- Move parallel setting for coverage calculation to tox.ini ([#7173](https://github.com/napari/napari/pull/7173))
+- Clarify workflow names ([#7174](https://github.com/napari/napari/pull/7174))
+- correct typos in comments ([#7175](https://github.com/napari/napari/pull/7175))
+- MNT Parametrize `test_open_files_dialog` to check for `stack` `True` and `False` ([#7176](https://github.com/napari/napari/pull/7176))
+- Update `babel`, `hypothesis`, `lxml`, `numpydoc`, `tifffile` ([#7179](https://github.com/napari/napari/pull/7179))
+- Remove `post` identifier when determine deploy directory ([docs#467](https://github.com/napari/docs/pull/467))
+
+## 12 authors added to this release (alphabetical)
+
+(+) denotes first-time contributors 🥳
+
+- [andrew sweet](https://github.com/napari/napari/commits?author=andy-sweet) - @andy-sweet
+- [Antoine J.-F. Salomon](https://github.com/napari/napari/commits?author=AJFSalomon) - @AJFSalomon +
+- [Ashley Anderson](https://github.com/napari/napari/commits?author=aganders3) - @aganders3
+- [Daniel Althviz Moré](https://github.com/napari/napari/commits?author=dalthviz) - @dalthviz
+- [Grzegorz Bokota](https://github.com/napari/napari/commits?author=Czaki) ([docs](https://github.com/napari/docs/commits?author=Czaki))  - @Czaki
+- [Johannes Soltwedel](https://github.com/napari/napari/commits?author=jo-mueller) - @jo-mueller
+- [Juan Nunez-Iglesias](https://github.com/napari/docs/commits?author=jni) - @jni
+- [kyle i. s. harrington](https://github.com/napari/docs/commits?author=kephale) - @kephale
+- [Lorenzo Gaifas](https://github.com/napari/napari/commits?author=brisvag) - @brisvag
+- [Lucy Liu](https://github.com/napari/napari/commits?author=lucyleeow) ([docs](https://github.com/napari/docs/commits?author=lucyleeow))  - @lucyleeow
+- [Melissa Weber Mendonça](https://github.com/napari/napari/commits?author=melissawm) ([docs](https://github.com/napari/docs/commits?author=melissawm))  - @melissawm
+- [Peter Sobolewski](https://github.com/napari/napari/commits?author=psobolewskiPhD) - @psobolewskiPhD
+
+## 13 reviewers added to this release (alphabetical)
+
+(+) denotes first-time contributors 🥳
+
+- [andrew sweet](https://github.com/napari/napari/commits?author=andy-sweet) - @andy-sweet
+- [Antoine J.-F. Salomon](https://github.com/napari/napari/commits?author=AJFSalomon) - @AJFSalomon +
+- [Ashley Anderson](https://github.com/napari/napari/commits?author=aganders3) - @aganders3
+- [Draga Doncila Pop](https://github.com/napari/docs/commits?author=DragaDoncila) - @DragaDoncila
+- [Grzegorz Bokota](https://github.com/napari/napari/commits?author=Czaki) ([docs](https://github.com/napari/docs/commits?author=Czaki))  - @Czaki
+- [Johannes Soltwedel](https://github.com/napari/napari/commits?author=jo-mueller) - @jo-mueller
+- [Jordão Bragantini](https://github.com/napari/docs/commits?author=JoOkuma) - @JoOkuma
+- [Juan Nunez-Iglesias](https://github.com/napari/docs/commits?author=jni) - @jni
+- [Lorenzo Gaifas](https://github.com/napari/napari/commits?author=brisvag) - @brisvag
+- [Lucy Liu](https://github.com/napari/napari/commits?author=lucyleeow) ([docs](https://github.com/napari/docs/commits?author=lucyleeow))  - @lucyleeow
+- [Melissa Weber Mendonça](https://github.com/napari/napari/commits?author=melissawm) ([docs](https://github.com/napari/docs/commits?author=melissawm))  - @melissawm
+- [Peter Sobolewski](https://github.com/napari/napari/commits?author=psobolewskiPhD) - @psobolewskiPhD
+- [Wouter-Michiel Vierdag](https://github.com/napari/docs/commits?author=melonora) - @melonora
+
diff --git a/docs/release/release_0_5_3.md b/docs/release/release_0_5_3.md
new file mode 100644
index 000000000..4c3ec52a6
--- /dev/null
+++ b/docs/release/release_0_5_3.md
@@ -0,0 +1,121 @@
+# napari 0.5.3
+
+*Friday, Aug 30, 2024*
+
+We’re happy to announce the release of napari 0.5.3!
+
+napari is a fast, interactive, multi-dimensional image viewer for Python. It’s designed for exploring, annotating, and analyzing multi-dimensional images. It’s built on Qt (for the GUI), VisPy (for performant GPU-based rendering), and the scientific Python stack (NumPy, SciPy, and friends).
+
+For more information, examples, and documentation, please visit our website: https://napari.org/
+
+## Highlights
+
+This is primarily a bug-fix release, including fixes for a couple of nasty
+regressions in 0.5.0 ([#7184](https://github.com/napari/napari/pull/7184)) and
+0.5.2 ([#7201](https://github.com/napari/napari/pull/7201)). However, we also
+have a couple of *excellent* user-facing improvements:
+
+- In [#7090](https://github.com/napari/napari/pull/7090), new contributor [Bean
+  Li](https://github.com/beanli161514) fixed a *very* long-standing issue in
+  napari: 3D picking didn't work when using a perspective projection (rather
+  than the default orthogonal projection. The result is glorious:
+
+  ![animated gif showing picking of points in 3D filaments using a perspective projection camera](https://github.com/user-attachments/assets/58036c3c-5776-4f13-bb49-562334b53834)
+
+  There's still a lot of work to be done in perspective projection (dragging
+  planes, for example, still doesn't work), but this is an exciting first step,
+  and we are thrilled that it came from a new community member! Thanks
+  [@beanli161514](https://github.com/beanli161514)!
+
+- In [#7146](https://github.com/napari/napari/pull/7146), napari team member
+  [Grzegorz Bokota](https://github.com/Czaki) fixed a long-standing issue in
+  napari: Layer.get_status used to be computed on the main thread, which meant
+  that layers for which this involved heavy computation (such as large Labels
+  layers, or Shapes layers or 3D surface layers with lots of polygons) would
+  slow down the viewer refresh rate. Grzegorz's changes move the computation to
+  a separate thread, which will dramatically improve performance in many
+  situations. 🚀🚀🚀
+
+Thanks as always to all our contributors, and read on for the full list of
+changes!
+
+## Improvements
+
+- [enh] Add a keybinding for rotating layer and alt-click on Transpose button ([#7052](https://github.com/napari/napari/pull/7052))
+- enable 3D picking with perspective camera ([#7090](https://github.com/napari/napari/pull/7090))
+- [UX/UI] Update layer controls tooltips ([#7153](https://github.com/napari/napari/pull/7153))
+- Update labels_with_features example for #7025 ([#7199](https://github.com/napari/napari/pull/7199))
+
+## Performance
+
+- Fix missing extent cache invalidation ([#7015](https://github.com/napari/napari/pull/7015))
+- Calculate status in a separate thread ([#7146](https://github.com/napari/napari/pull/7146))
+- If a shape is convex, use faster fan triangulation ([#7214](https://github.com/napari/napari/pull/7214))
+- Speed up highlighting in the Shapes layer ([#7223](https://github.com/napari/napari/pull/7223))
+
+## Bug Fixes
+
+- Fix missing extent cache invalidation ([#7015](https://github.com/napari/napari/pull/7015))
+- enable 3D picking with perspective camera ([#7090](https://github.com/napari/napari/pull/7090))
+- Implement shortcuts widget `setValue` to handle shortcuts settings updates ([#7180](https://github.com/napari/napari/pull/7180))
+- Fix bug preventing from change symbol for points initialized with single value ([#7184](https://github.com/napari/napari/pull/7184))
+- Add `napari.benchmarks.util` to sdist and wheel to fix balls example data ([#7186](https://github.com/napari/napari/pull/7186))
+- Bugfix: Revert "Emit highlight event only if selection changed (#7162)" ([#7201](https://github.com/napari/napari/pull/7201))
+- Use new DOI for surface example ([#7222](https://github.com/napari/napari/pull/7222))
+-  Fix convex polygon detection ([#7228](https://github.com/napari/napari/pull/7228))
+
+## Documentation
+
+- Use new DOI for surface example ([#7222](https://github.com/napari/napari/pull/7222))
+- Add 0.5.3 release notes ([docs#485](https://github.com/napari/docs/pull/485))
+- Update 0.5.3 release notes with new bugfix ([docs#487](https://github.com/napari/docs/pull/487))
+- Add short guide on updating constraints files ([docs#460](https://github.com/napari/docs/pull/460))
+- Add 0.5.2 to the version switcher ([docs#479](https://github.com/napari/docs/pull/479))
+- Minor improvement to `qtbot` testing section ([docs#481](https://github.com/napari/docs/pull/481))
+- Improve informations on community page ([docs#482](https://github.com/napari/docs/pull/482))
+
+## Other Pull Requests
+
+- Fix/add some typing to napari.layers.tracks ([#7014](https://github.com/napari/napari/pull/7014))
+- Call workflow providing target directory name ([#7181](https://github.com/napari/napari/pull/7181))
+- Improve error message in `combine_widgets` ([#7194](https://github.com/napari/napari/pull/7194))
+- [Maint] Remove some pytest skipif for python <3.9 ([#7203](https://github.com/napari/napari/pull/7203))
+- Update `dask`, `hypothesis`, `imageio`, `matplotlib` ([#7206](https://github.com/napari/napari/pull/7206))
+- [pre-commit.ci] pre-commit autoupdate ([#7207](https://github.com/napari/napari/pull/7207))
+- [pre-commit.ci] pre-commit autoupdate ([#7216](https://github.com/napari/napari/pull/7216))
+- Fix example by connect missing event ([#7218](https://github.com/napari/napari/pull/7218))
+- Improve deploy workflow by use deploy directory from workflow dispatch input  ([docs#477](https://github.com/napari/docs/pull/477))
+
+## 9 authors added to this release (alphabetical)
+
+(+) denotes first-time contributors 🥳
+
+- [BeanLi](https://github.com/napari/napari/commits?author=beanli161514) - @beanli161514 +
+- [Daniel Althviz Moré](https://github.com/napari/napari/commits?author=dalthviz) - @dalthviz
+- [David Stansby](https://github.com/napari/napari/commits?author=dstansby) - @dstansby
+- [Grzegorz Bokota](https://github.com/napari/napari/commits?author=Czaki) ([docs](https://github.com/napari/docs/commits?author=Czaki))  - @Czaki
+- [Juan Nunez-Iglesias](https://github.com/napari/napari/commits?author=jni) ([docs](https://github.com/napari/docs/commits?author=jni))  - @jni
+- [Lorenzo Gaifas](https://github.com/napari/napari/commits?author=brisvag) - @brisvag
+- [Lucy Liu](https://github.com/napari/napari/commits?author=lucyleeow) ([docs](https://github.com/napari/docs/commits?author=lucyleeow))  - @lucyleeow
+- [Melissa Weber Mendonça](https://github.com/napari/docs/commits?author=melissawm) - @melissawm
+- [Peter Sobolewski](https://github.com/napari/napari/commits?author=psobolewskiPhD) - @psobolewskiPhD
+
+
+## 13 reviewers added to this release (alphabetical)
+
+(+) denotes first-time contributors 🥳
+
+- [BeanLi](https://github.com/napari/napari/commits?author=beanli161514) - @beanli161514 +
+- [Daniel Althviz Moré](https://github.com/napari/napari/commits?author=dalthviz) - @dalthviz
+- [David Stansby](https://github.com/napari/napari/commits?author=dstansby) - @dstansby
+- [Draga Doncila Pop](https://github.com/napari/docs/commits?author=DragaDoncila) - @DragaDoncila
+- [Genevieve Buckley](https://github.com/napari/docs/commits?author=GenevieveBuckley) - @GenevieveBuckley
+- [Grzegorz Bokota](https://github.com/napari/napari/commits?author=Czaki) ([docs](https://github.com/napari/docs/commits?author=Czaki))  - @Czaki
+- [Juan Nunez-Iglesias](https://github.com/napari/napari/commits?author=jni) ([docs](https://github.com/napari/docs/commits?author=jni))  - @jni
+- [Kevin Yamauchi](https://github.com/napari/docs/commits?author=kevinyamauchi) - @kevinyamauchi
+- [Lorenzo Gaifas](https://github.com/napari/napari/commits?author=brisvag) - @brisvag
+- [Lucy Liu](https://github.com/napari/napari/commits?author=lucyleeow) ([docs](https://github.com/napari/docs/commits?author=lucyleeow))  - @lucyleeow
+- [Melissa Weber Mendonça](https://github.com/napari/docs/commits?author=melissawm) - @melissawm
+- [Peter Sobolewski](https://github.com/napari/napari/commits?author=psobolewskiPhD) - @psobolewskiPhD
+- [Wouter-Michiel Vierdag](https://github.com/napari/docs/commits?author=melonora) - @melonora
+
diff --git a/docs/release/release_0_5_4.md b/docs/release/release_0_5_4.md
new file mode 100644
index 000000000..e86612fb3
--- /dev/null
+++ b/docs/release/release_0_5_4.md
@@ -0,0 +1,142 @@
+# napari 0.5.4
+
+*Monday, Sep 30, 2024*
+
+We’re happy to announce the release of napari 0.5.4!
+
+napari is a fast, interactive, multi-dimensional image viewer for Python. It’s designed for exploring, annotating, and analyzing multi-dimensional images. It’s built on Qt (for the GUI), VisPy (for performant GPU-based rendering), and the scientific Python stack (NumPy, SciPy, and friends).
+
+For more information, examples, and documentation, please visit our website: https://napari.org/
+
+## Highlights
+
+Another release with a lot of bug fixes, but also some (more!) improvements to
+Shapes layer performance ([#7144](https://github.com/napari/napari/pull/7144),
+[#7256](https://github.com/napari/napari/pull/7256)), and a few nice
+usability/quality of life features!
+
+- you can now follow the value under the cursor around in images in 3D view as
+  well as 2D ([#7126](https://github.com/napari/napari/pull/7126))
+- Use standard keyboard shortcuts to zoom in and out ({kbd}`Command/Ctrl+=`,
+  {kbd}`Command/Ctrl+-`) and to zoom-to-fit ({kbd}`Command/Ctrl+0`)
+  ([#7200](https://github.com/napari/napari/pull/7200))
+- you can now save tiff files larger than 4GB
+  ([#7242](https://github.com/napari/napari/pull/7242))
+
+Finally, we're starting some work on tweaking the UI to make it more
+self-consistent, with the ultimate goal of adding functionality such as showing
+common controls when multiple layers are selected, so that, for example, you
+can select multiple layers and adjust all their opacity settings together. As
+the first step for this, the *layer blending* controls have been moved directly
+under the opacity control, so that all per-layer controls are next to each
+other in the UI ([#7202](https://github.com/napari/napari/pull/7202))
+
+Read on for all the changes in this version!
+
+
+## New Features
+
+- enable get_value_3d for image layers ([#7126](https://github.com/napari/napari/pull/7126))
+- Preserve area of dock widgets between sessions ([#7247](https://github.com/napari/napari/pull/7247))
+
+## Improvements
+
+- Speed up `get_status` for Shapes layer by using bounding boxes ([#7144](https://github.com/napari/napari/pull/7144))
+- Enh: Add zoom options and keybindings to View menu ([#7200](https://github.com/napari/napari/pull/7200))
+- [ux/ui] Put blending controls under opacity slider in layer controls ([#7202](https://github.com/napari/napari/pull/7202))
+- Enable conflicts detection with layer keybindings when changing viewer ones and add group info to conflicts popup ([#7231](https://github.com/napari/napari/pull/7231))
+- Speedup `_is_convex` by avoid calling `np.roll` ([#7256](https://github.com/napari/napari/pull/7256))
+- Sort plugin manifests in alphabetical order for registration ([#7266](https://github.com/napari/napari/pull/7266))
+
+## Performance
+
+- Speed up `get_status` for Shapes layer by using bounding boxes ([#7144](https://github.com/napari/napari/pull/7144))
+- Speedup `_is_convex` by avoid calling `np.roll` ([#7256](https://github.com/napari/napari/pull/7256))
+
+## Bug Fixes
+
+- start/stop status thread on show/hide main window ([#7240](https://github.com/napari/napari/pull/7240))
+- Added support for saving tiff files > 4GB :) ([#7242](https://github.com/napari/napari/pull/7242))
+- Accept any Mapping as output of a plugin widget ([#7250](https://github.com/napari/napari/pull/7250))
+- Eliminate nearly all Qt widget leaks by using qtbot ([#7251](https://github.com/napari/napari/pull/7251))
+- Enforce minimum side length when guessing if image is RGB ([#7273](https://github.com/napari/napari/pull/7273))
+- Remove skip conditions for PySide2/6 over plugins menu tests and bump `napari-plugin-manager` minimum version (>=0.1.3) ([#7293](https://github.com/napari/napari/pull/7293))
+- Fix color shuffling for bool labels ([#7294](https://github.com/napari/napari/pull/7294))
+- Fix cursor dimensionality race condition ([#7295](https://github.com/napari/napari/pull/7295))
+- Fix overflow error in shuffle colormap for signed integer labels ([#7296](https://github.com/napari/napari/pull/7296))
+- When calculating view directions, check ndim, not just ndisplay ([#7301](https://github.com/napari/napari/pull/7301))
+
+## Documentation
+
+- Add beanli161514 to citation file ([#7272](https://github.com/napari/napari/pull/7272))
+- Doc/metadata: add jni's ORCID to the CITATION.cff file ([#7275](https://github.com/napari/napari/pull/7275))
+- Style fix: use recommended capitalization for "GitHub" in README ([#7284](https://github.com/napari/napari/pull/7284))
+- Add psygnal and pydantic to napari --info ([#7285](https://github.com/napari/napari/pull/7285))
+- Move images to _static folder ([docs#483](https://github.com/napari/docs/pull/483))
+- Update version switcher to add 0.5.3 ([docs#488](https://github.com/napari/docs/pull/488))
+- Move release notes to be under Usage ([docs#489](https://github.com/napari/docs/pull/489))
+- Update release guide ([docs#491](https://github.com/napari/docs/pull/491))
+- Use `get_qapp` or `get_app_model` instead of `get_app` ([docs#495](https://github.com/napari/docs/pull/495))
+- Add 0.5.4 release notes ([docs#496](https://github.com/napari/docs/pull/496))
+- Add note about questions in landing page ([docs#498](https://github.com/napari/docs/pull/498))
+- Add further fixes to release notes ([docs#499](Add further fixes to release notes))
+
+## Other Pull Requests
+
+- Update script for vendored modules ([#5779](https://github.com/napari/napari/pull/5779))
+- Update `certifi`, `dask`, `hypothesis`, `ipython`, `numpy`, `qtconsole`, `rich`, `scipy`, `tifffile` ([#7212](https://github.com/napari/napari/pull/7212))
+- Block zarr 3.0.0a1 and 3.0.0a2 in pre-release tests ([#7217](https://github.com/napari/napari/pull/7217))
+- Add autouse fixture that clears cached property `Action.injected` ([#7224](https://github.com/napari/napari/pull/7224))
+- Update `tifffile` ([#7235](https://github.com/napari/napari/pull/7235))
+- CI benchmark run comment will now include results table ([#7237](https://github.com/napari/napari/pull/7237))
+- [pre-commit.ci] pre-commit autoupdate ([#7239](https://github.com/napari/napari/pull/7239))
+- Fix coverage and debug artifacts upload ([#7241](https://github.com/napari/napari/pull/7241))
+- Replaced broken link to the "Translations" page :) ([#7243](https://github.com/napari/napari/pull/7243))
+- Alow to call benchmark that do not have params ([#7252](https://github.com/napari/napari/pull/7252))
+- Block zarr=3.0.0a3 to fix pre-release tests ([#7254](https://github.com/napari/napari/pull/7254))
+- Change type of layer Metadata from dict to Mapping ([#7257](https://github.com/napari/napari/pull/7257))
+- Update `fsspec`, `hypothesis`, `pydantic`, `tensorstore`, `virtualenv`, `zarr` ([#7258](https://github.com/napari/napari/pull/7258))
+- Deprecate usage of `get_app` functions to get `QApplication` or `NapariApplication` instances ([#7269](https://github.com/napari/napari/pull/7269))
+- Block `zarr==3.0.0a4` ([#7271](https://github.com/napari/napari/pull/7271))
+- Update `dask`, `hypothesis`, `napari-plugin-manager`, `pandas`, `pydantic`, `pytest`, `rich`, `tifffile`, `virtualenv`, `xarray` ([#7274](https://github.com/napari/napari/pull/7274))
+- [pre-commit.ci] pre-commit autoupdate ([#7276](https://github.com/napari/napari/pull/7276))
+- Fix `test_windows_grouping_overwrite` skip condition and asserts ([#7281](https://github.com/napari/napari/pull/7281))
+- Update menu sorting tests still using `mock_app` and `get_app` instead of `mock_app_model` and `get_app_model` ([#7283](https://github.com/napari/napari/pull/7283))
+- Remove obsolete self from layout argument ([#7291](https://github.com/napari/napari/pull/7291))
+
+
+## 11 authors added to this release (alphabetical)
+
+(+) denotes first-time contributors 🥳
+
+- [BeanLi](https://github.com/napari/napari/commits?author=beanli161514) - @beanli161514
+- [Daniel Althviz Moré](https://github.com/napari/napari/commits?author=dalthviz) ([docs](https://github.com/napari/docs/commits?author=dalthviz))  - @dalthviz
+- [Draga Doncila Pop](https://github.com/napari/napari/commits?author=DragaDoncila) - @DragaDoncila
+- [Grzegorz Bokota](https://github.com/napari/napari/commits?author=Czaki) - @Czaki
+- [Ikko Eltociear Ashimine](https://github.com/napari/napari/commits?author=eltociear) - @eltociear +
+- [Juan Nunez-Iglesias](https://github.com/napari/napari/commits?author=jni) ([docs](https://github.com/napari/docs/commits?author=jni))  - @jni
+- [Lorenzo Gaifas](https://github.com/napari/napari/commits?author=brisvag) - @brisvag
+- [Lucy Liu](https://github.com/napari/napari/commits?author=lucyleeow) - @lucyleeow
+- [Melissa Weber Mendonça](https://github.com/napari/docs/commits?author=melissawm) - @melissawm
+- [Peter Sobolewski](https://github.com/napari/napari/commits?author=psobolewskiPhD) - @psobolewskiPhD
+- [Sammy Hansali](https://github.com/napari/napari/commits?author=sammyhansali) - @sammyhansali +
+
+
+## 13 reviewers added to this release (alphabetical)
+
+(+) denotes first-time contributors 🥳
+
+- [andrew sweet](https://github.com/napari/docs/commits?author=andy-sweet) - @andy-sweet
+- [Ashley Anderson](https://github.com/napari/docs/commits?author=aganders3) - @aganders3
+- [Daniel Althviz Moré](https://github.com/napari/napari/commits?author=dalthviz) ([docs](https://github.com/napari/docs/commits?author=dalthviz))  - @dalthviz
+- [Draga Doncila Pop](https://github.com/napari/napari/commits?author=DragaDoncila) - @DragaDoncila
+- [Grzegorz Bokota](https://github.com/napari/napari/commits?author=Czaki) - @Czaki
+- [jaime rodriguez-guerra](https://github.com/napari/docs/commits?author=jaimergp) - @jaimergp
+- [Juan Nunez-Iglesias](https://github.com/napari/napari/commits?author=jni) ([docs](https://github.com/napari/docs/commits?author=jni))  - @jni
+- [kyle i. s. harrington](https://github.com/napari/docs/commits?author=kephale) - @kephale
+- [Lorenzo Gaifas](https://github.com/napari/napari/commits?author=brisvag) - @brisvag
+- [Lucy Liu](https://github.com/napari/napari/commits?author=lucyleeow) - @lucyleeow
+- [Melissa Weber Mendonça](https://github.com/napari/docs/commits?author=melissawm) - @melissawm
+- [Peter Sobolewski](https://github.com/napari/napari/commits?author=psobolewskiPhD) - @psobolewskiPhD
+- [Wouter-Michiel Vierdag](https://github.com/napari/docs/commits?author=melonora) - @melonora
+
diff --git a/docs/roadmaps/0_3.md b/docs/roadmaps/0_3.md
index d6b18c36e..f6755600e 100644
--- a/docs/roadmaps/0_3.md
+++ b/docs/roadmaps/0_3.md
@@ -18,7 +18,7 @@ Once the above goals are met, we will develop napari's capabilities for image pr
 
 - **Better support for viewing big datasets**. Currently, napari is fast when viewing on-disk datasets that can be naturally sliced along one axis (e.g. a time series) *and where loading one slice is fast*. However, when the loading is slow, the napari UI itself becomes slow, sometimes to the point of being unusable. We aim to improve this by making views and interactions non-blocking ([#845](https://github.com/napari/napari/issues/845)), and improving caching ([#718](https://github.com/napari/napari/issues/718)). We will also ensure that napari can be used `headless` without the GUI.
 
-- **Improving the performance of operations on in-memory data**. Even when data is loaded in memory, some operations, such as label and shape painting, slicing along large numbers of points, or adjusting contrast and gamma, can be slow. We will continue developing our [benchmark suite](https://github.com/napari/docs/blob/main/docs/developers/benchmarks.md) and work to integrate it into our development process. See the [`performance` label](https://github.com/napari/napari/labels/performance) for a current list of issues related to performance.
+- **Improving the performance of operations on in-memory data**. Even when data is loaded in memory, some operations, such as label and shape painting, slicing along large numbers of points, or adjusting contrast and gamma, can be slow. We will continue developing our [benchmark suite](https://github.com/napari/docs/blob/main/docs/developers/contributing/performance/benchmarks.md) and work to integrate it into our development process. See the [`performance` label](https://github.com/napari/napari/labels/performance) for a current list of issues related to performance.
 
 - Add a unified **world coordinate system**. Scientists need to measure data that comes from a real space with physical dimensions. Currently, napari has no concept of the space in which data lives: everything is unitless. Further, it is unclear at various parts in the UI whether a coordinate has been transformed. And finally, some data are acquired with distortions, such as skew in data collected on stage-scanning lightsheet microscopes, and napari should be able to account for those distortions by chaining together transforms - including affine and ultimately deformable transforms. We are tracking progress in this area in the [World Coordinates project board](https://github.com/napari/napari/projects/10).
 
@@ -44,9 +44,9 @@ Once the above goals are met, we will develop napari's capabilities for image pr
 
 ## Provide accessible documentation, tutorials, and demos
 
-- Improve our website [napari.org](https://napari.org) to provide easy access to all napari related materials, including the [**four types of documentation**](https://www.divio.com/blog/documentation/): learning-oriented tutorials, goal-oriented how-to-guides or galleries, understanding-oriented explanations (including developer resources), and a comprehensive API reference. See [#764](https://github.com/napari/napari/issues/764) and the [`documentation` label](https://github.com/napari/napari/labels/documentation) on the napari repository for more details.
+- Improve our website [napari.org](https://napari.org) to provide easy access to all napari related materials, including the [**four types of documentation**](https://docs.divio.com/documentation-system/): learning-oriented tutorials, goal-oriented how-to-guides or galleries, understanding-oriented explanations (including developer resources), and a comprehensive API reference. See [#764](https://github.com/napari/napari/issues/764) and the [`documentation` label](https://github.com/napari/napari/labels/documentation) on the napari repository for more details.
 
-- Add a **napari human interface guide** for plugin developers, akin to [Apple's Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/guidelines/overview/). We want such a guide to promote best practices and ensure that plugins provide a consistent user experience.
+- Add a **napari human interface guide** for plugin developers, akin to [Apple's Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/). We want such a guide to promote best practices and ensure that plugins provide a consistent user experience.
 
 ## Work prioritized for future roadmaps
 
diff --git a/docs/roadmaps/0_3_retrospective.md b/docs/roadmaps/0_3_retrospective.md
index 9916ec034..b74811dd6 100644
--- a/docs/roadmaps/0_3_retrospective.md
+++ b/docs/roadmaps/0_3_retrospective.md
@@ -77,11 +77,11 @@ Once the above goals are met, we will develop napari's capabilities for image pr
 
 ## Provide accessible documentation, tutorials, and demos
 
-- Improve our website [napari.org](https://napari.org) to provide easy access to all napari related materials, including the [**four types of documentation**](https://www.divio.com/blog/documentation/): learning-oriented tutorials, goal-oriented how-to-guides or galleries, understanding-oriented explanations (including developer resources), and a comprehensive API reference. See [#764](https://github.com/napari/napari/issues/764) and the [`documentation` label](https://github.com/napari/napari/labels/documentation) on the napari repository for more details.
+- Improve our website [napari.org](https://napari.org) to provide easy access to all napari related materials, including the [**four types of documentation**](https://docs.divio.com/documentation-system/): learning-oriented tutorials, goal-oriented how-to-guides or galleries, understanding-oriented explanations (including developer resources), and a comprehensive API reference. See [#764](https://github.com/napari/napari/issues/764) and the [`documentation` label](https://github.com/napari/napari/labels/documentation) on the napari repository for more details.
 
     > We have begun the design work for this but have not begun the implementation yet. This work will be moved to our 0.4 series of releases.
 
-- Add a **napari human interface guide** for plugin developers, akin to [Apple's Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/guidelines/overview/). We want such a guide to promote best practices and ensure that plugins provide a consistent user experience.
+- Add a **napari human interface guide** for plugin developers, akin to [Apple's Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines). We want such a guide to promote best practices and ensure that plugins provide a consistent user experience.
 
     > We have not done this work yet, and this work will be moved to our 0.4 series of releases.
 
diff --git a/docs/roadmaps/0_4.md b/docs/roadmaps/0_4.md
index b19567e46..c4f1c4b05 100644
--- a/docs/roadmaps/0_4.md
+++ b/docs/roadmaps/0_4.md
@@ -107,7 +107,7 @@ Quality documentation is therefore high priority for the team. We aim to:
 
 - Support autogenerated screenshots and movies for our documentation to ensures it always stays up-to-date as we improve napari. These examples should also be runnable by our users to serve as training materials as they learn to use napari.
 
-- Add a **napari human interface guide** for plugin developers, akin to [Apple's Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/guidelines/overview/). We want such a guide to promote best practices and ensure that plugins provide a consistent user experience.
+- Add a **napari human interface guide** for plugin developers, akin to [Apple's Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines). We want such a guide to promote best practices and ensure that plugins provide a consistent user experience.
 
 ## Work prioritized for future roadmaps
 
diff --git a/docs/tutorials/annotation/annotate_points.md b/docs/tutorials/annotation/annotate_points.md
index 0a2afbc25..2b5f45573 100644
--- a/docs/tutorials/annotation/annotate_points.md
+++ b/docs/tutorials/annotation/annotate_points.md
@@ -435,7 +435,7 @@ Once we are happy with the annotations, we can save them to a CSV file using the
 To do so, first, select the "Points" layer in the layer list and then click "Save Selected layer(s)"  in the "File" menu or press control+S (cmd+S on Mac OS)  to bring up the file save dialog.
 From here you can enter the file path and save the annotation coordinates as a CSV.
 
-![Viewer with green box around a points layer in layer list. Label in green says "1. Select Points layer in the layer list". Dialog in the middle of the viewer has options to add save file name and choose save location, with Cancel and Save buttons in the bottom right.](../assets/tutorials/points_save_dialog.png)
+![Viewer with green box around a points layer in layer list. Label in green says "1. Select Points layer in the layer list". Dialog in the middle of the viewer has options to add save file name and choose save location, with Cancel and Save buttons in the bottom right.](../../_static/images/points_save_dialog.png)
 
 Alternatively, we can use the `points_layer.save()` method to save the coordinates from the points layer to a CSV file.
 We can enter the command either in the script (e.g., bind a save function to a hot key) or the napari terminal.
diff --git a/docs/tutorials/fundamentals/getting_started.md b/docs/tutorials/fundamentals/getting_started.md
index 95e761345..b3d878f7f 100644
--- a/docs/tutorials/fundamentals/getting_started.md
+++ b/docs/tutorials/fundamentals/getting_started.md
@@ -31,7 +31,7 @@ napari
 
 This command will launch an empty viewer:
 
-![image: an empty napari viewer](../assets/tutorials/launch_cli_empty.png)
+![image: an empty napari viewer](../../_static/images/launch_cli_empty.png)
 
 Once you have the viewer open you can add images through the `File -> Open` dropdown menu
 or by dragging and dropping images directly on the viewer. We currently only support files that can be read with [`skimage.io.imread`](https://scikit-image.org/docs/dev/api/skimage.io.html#skimage.io.imread),
@@ -45,7 +45,7 @@ napari my_image.png
 
 If the image is `RGB` or `RGBA` use the `-r` or `--rgb` flag.
 
-![image: napari viewer displaying an image layer](../assets/tutorials/launch_cli_image.png)
+![image: napari viewer displaying an image layer](../../_static/images/launch_cli_image.png)
 
 Launching `napari` directly from the command line is the simplest and fastest way to open the viewer,
 but it doesn't allow you to preprocess your images before opening them.
@@ -109,7 +109,7 @@ python my_example_script.py
 The [examples gallery](../../gallery) consists of code examples which can be
 downloaded as `.py` (and `.ipynb` files) and run as above.
 
-![image: napari launched from a python script](../assets/tutorials/launch_script.png)
+![image: napari launched from a python script](../../_static/images/launch_script.png)
 
 An advantage of launching `napari` from a python script
 is that you can preprocess your images and add multiple layers before displaying the viewer.
@@ -139,7 +139,7 @@ viewer, image_layer = napari.imshow(cells3d())
 loop](https://ipython.readthedocs.io/en/stable/config/eventloops.html#integrating-with-gui-event-loops)
 from IPython
 
-![image: napari launched from ipython](../assets/tutorials/launch_ipython.png)
+![image: napari launched from ipython](../../_static/images/launch_ipython.png)
 
 An advantage of launching napari from an IPython console
 is that the you can continue to programmatically interact with the viewer from the IPython console,
@@ -154,9 +154,9 @@ You can also launch `napari` from a Jupyter notebook. The
 [examples gallery](../../gallery), as mentioned above, can also be downloaded as
 `.ipynb` which can be run from a Jupyter notebook.
 
-Below, we launch the [notebook example](https://github.com/napari/napari/tree/main/examples/notebook.ipynb) from a Jupyter notebook.
+Below, we launch the [notebook example](https://github.com/napari/napari/blob/main/examples/notebook.ipynb) from a Jupyter notebook.
 
-![image: napari launched from a Jupyter notebook](../assets/tutorials/launch_jupyter.png)
+![image: napari launched from a Jupyter notebook](../../_static/images/launch_jupyter.png)
 
 Similar to launching from the IPython console,
 an advantage of launching `napari` from a Jupyter notebook
diff --git a/docs/tutorials/fundamentals/installation.md b/docs/tutorials/fundamentals/installation.md
index aec5d0400..155087ae9 100644
--- a/docs/tutorials/fundamentals/installation.md
+++ b/docs/tutorials/fundamentals/installation.md
@@ -153,7 +153,7 @@ napari
 
 An empty napari viewer should appear as follows:
 
-![macOS desktop with a napari viewer window without any image opened in the foreground, and a terminal in the background with the appropriate conda environment activated (if applicable) and the command to open napari entered.](../assets/tutorials/launch_cli_empty.png)
+![macOS desktop with a napari viewer window without any image opened in the foreground, and a terminal in the background with the appropriate conda environment activated (if applicable) and the command to open napari entered.](../../_static/images/launch_cli_empty.png)
 
 ````{note}
 On some platforms, particularly macOS and Windows, there may be a ~30 second
@@ -171,8 +171,8 @@ the current release {{ napari_version }}, using the command: `napari --version`
 
 napari needs a library called [Qt](https://www.qt.io/) to run its user interface
 (UI). In Python, there are two alternative libraries to run this, called
-[PyQt5](https://www.riverbankcomputing.com/software/pyqt/download5) and
-[PySide2](https://doc.qt.io/qtforpython/). By default, we don't choose for you,
+[PyQt5](https://www.riverbankcomputing.com/software/pyqt/download) and
+[PySide2](https://doc.qt.io/qtforpython-6/). By default, we don't choose for you,
 and simply running `python -m pip install napari` will not install either. You *might*
 already have one of them installed in your environment, thanks to other
 scientific packages such as Spyder or matplotlib. If neither is available,
@@ -253,6 +253,6 @@ guidelines](napari-contributing)
 - if you are running into issues or bugs, please open a [new issue](https://github.com/napari/napari/issues/new/choose) on our [issue
 tracker](https://github.com/napari/napari/issues)
 - if you want help using napari, we are a community partner on the [imagesc
-forum](https://forum.image.sc/tags/napari) and all usage support requests should
+forum](https://forum.image.sc/tag/napari) and all usage support requests should
 be posted on the forum with the tag `napari`. We look forward to interacting
 with you there!
diff --git a/docs/tutorials/fundamentals/installation_bundle_conda.md b/docs/tutorials/fundamentals/installation_bundle_conda.md
index 6a51cf064..dde12a7e4 100644
--- a/docs/tutorials/fundamentals/installation_bundle_conda.md
+++ b/docs/tutorials/fundamentals/installation_bundle_conda.md
@@ -33,7 +33,7 @@ To start, visit the [latest napari release page](https://github.com/napari/napar
   - For Apple processors, download the `*-macOS-arm64.pkg` installer.
 - Linux users will need to choose the `*-Linux-x86_64.sh` installer.
 
-![Cropped screenshot of the GitHub Releases page for napari version 0.4.15. The expanded assets tab shows a number of installers available for different operating systems and architectures. Yellow rectangles highlight the files that correspond to the conda-based installers described in this tutorial.](../assets/tutorials/installation/bundle_02.png)
+![Cropped screenshot of the GitHub Releases page for napari version 0.4.15. The expanded assets tab shows a number of installers available for different operating systems and architectures. Yellow rectangles highlight the files that correspond to the conda-based installers described in this tutorial.](../../_static/images/bundle_02.png)
 
 ```{note}
 If you are interested in an earlier version of napari, you may access those files by scrolling below the latest release on the [napari release page](https://github.com/napari/napari/releases). The instructions below will work for napari versions 0.4.15 and above.
@@ -47,19 +47,19 @@ This installation method does not have any prerequisites.
 
 Once you have downloaded the appropriate macOS package file, you will have a file with a name like `napari-0.5.0-macOS-x86_64.pkg`. Double click this file to open the installer.
 
-![Cropped screenshot of macOS desktop UI showing the icon of the PKG installer file, and an arrow pointing to the Welcome page in the opened PKG installer.](../assets/tutorials/installation/bundle_04.png)
+![Cropped screenshot of macOS desktop UI showing the icon of the PKG installer file, and an arrow pointing to the Welcome page in the opened PKG installer.](../../_static/images/bundle_04.png)
 
 Click 'Continue' to open the Software License Agreement.
 
-![Cropped screenshot of the License page in an opened PKG installer, showing the BSD 3-Clause License text and four buttons: Print, Save, Go Back and Continue.](../assets/tutorials/installation/bundle_06.png)
+![Cropped screenshot of the License page in an opened PKG installer, showing the BSD 3-Clause License text and four buttons: Print, Save, Go Back and Continue.](../../_static/images/bundle_06.png)
 
 After reading this agreement, click 'Continue' to be prompted to agree to the Software License Agreement in order to proceed with installation.
 
-![Cropped screenshot of the License page prompting the user to agree to the napari Software License Agreement. The dialog contains three buttons: Read License, Disagree and Agree.](../assets/tutorials/installation/bundle_07.png)
+![Cropped screenshot of the License page prompting the user to agree to the napari Software License Agreement. The dialog contains three buttons: Read License, Disagree and Agree.](../../_static/images/bundle_07.png)
 
 Click on 'Agree'. On the following page, you will be shown how much space the installation will use and can begin the standard installation by clicking 'Install.'
 
-![Cropped screenshot of the Installation Type page on the PKG installer. It reports the estimated space the installation will use (2.45 GB in this example) and shows four buttons: Change Install Location, Customize, Go Back and Install.](../assets/tutorials/installation/bundle_09.png)
+![Cropped screenshot of the Installation Type page on the PKG installer. It reports the estimated space the installation will use (2.45 GB in this example) and shows four buttons: Change Install Location, Customize, Go Back and Install.](../../_static/images/bundle_09.png)
 
 However, if you would like to change the default location for the installation, you may specify a different location by clicking 'Change Install Location…' and following the subsequent prompts before starting the installation.
 
@@ -67,7 +67,7 @@ You can also optionally click on 'Customize' to disable or enable some aspects o
 
 The installation progress can be monitored on the following window. Some notifications will appear in the top right corner of your display with further details.
 
-![Cropped screenshot of the Installation page of the PKG installer. This page displays a progress bar at a 10%. In the top right corner, an example of a system notification with the text 'Installing packages. This might take a few minutes' is shown](../assets/tutorials/installation/bundle_10.png)
+![Cropped screenshot of the Installation page of the PKG installer. This page displays a progress bar at a 10%. In the top right corner, an example of a system notification with the text 'Installing packages. This might take a few minutes' is shown](../../_static/images/bundle_10.png)
 
 ```{note}
 If an error ocurred during the installation, do not close the installer immediately. Before doing so, please inspect the logs by clicking on Window > Installer log or pressing <kbd>⌘</kbd> + <kbd>L</kbd>. In the Detail Level dropdown, choose 'Show All Logs' and click on Save to keep a copy of the contents in a text file. This will be useful if you want to [submit an issue](https://github.com/napari/napari/issues/new/choose).
@@ -75,11 +75,11 @@ If an error ocurred during the installation, do not close the installer immediat
 
 After finishing with no errors, a new page with the text "The installation was successful" will appear, as shown below.
 
-![Cropped screenshot of the final page of the PKG installer, Summary, reporting "The installation was successful" with a green check mark icon. A blue Close button is available.](../assets/tutorials/installation/bundle_11.png)
+![Cropped screenshot of the final page of the PKG installer, Summary, reporting "The installation was successful" with a green check mark icon. A blue Close button is available.](../../_static/images/bundle_11.png)
 
 Click Close to finish. You can now get started using napari! Use Launchpad to open the application.
 
-![Montage of two cropped screenshots. On the left, the macOS finder icon and the Launchpad icon, highlighted with a red circle. On the right, the opened launchpad UI showing a 4x4 grid of applications icon, with napari appearing in the bottom right corner.](../assets/tutorials/installation/bundle_13.png)
+![Montage of two cropped screenshots. On the left, the macOS finder icon and the Launchpad icon, highlighted with a red circle. On the right, the opened launchpad UI showing a 4x4 grid of applications icon, with napari appearing in the bottom right corner.](../../_static/images/bundle_13.png)
 
 ```{note}
 The first time you open napari you must use the Launchpad, but in subsequent uses, the napari application should show up in Spotlight search (<kbd>⌘</kbd> + <kbd>spacebar</kbd>). The application shortcut will also be available in Finder, under 🏠 [User directory] > Applications.
@@ -93,27 +93,27 @@ Next check out our [tutorial on the viewer](viewer.md) or explore any of the pag
 
 Once you have downloaded the Windows executable file, you will have a file with a name like `napari-0.5.0-Windows-x86_64.exe`. Double click this file to open the napari Setup.
 
-![Montage of the napari EXE installer icon with an arrow pointing to the Welcome page of the napari EXE installer on Windows.](../assets/tutorials/installation/bundle_17.png)
+![Montage of the napari EXE installer icon with an arrow pointing to the Welcome page of the napari EXE installer on Windows.](../../_static/images/bundle_17.png)
 
 Click Next to continue and go to the License page. Read the contents and, if you agree, continue by clicking 'I Agree'.
 
-![Cropped screenshot of the License Agreement page of the napari EXE installer. A scrollable text area displays the legal text. Three buttons are available: Back, I Agree, and Cancel.](../assets/tutorials/installation/bundle_18.png)
+![Cropped screenshot of the License Agreement page of the napari EXE installer. A scrollable text area displays the legal text. Three buttons are available: Back, I Agree, and Cancel.](../../_static/images/bundle_18.png)
 
 The recommended installation method is to install napari just for the current user ("Just Me"):
 
-![Cropped screenshot of the Setup Instalation Type page of the napari EXE installer. Two options are available: Just Me (recommended), and All Users (requires admin privileges). At the bottom, three buttons Back, Next and Cancel are displayed.](../assets/tutorials/installation/bundle_19.png)
+![Cropped screenshot of the Setup Instalation Type page of the napari EXE installer. Two options are available: Just Me (recommended), and All Users (requires admin privileges). At the bottom, three buttons Back, Next and Cancel are displayed.](../../_static/images/bundle_19.png)
 
 On the next page you will be shown how much space will be used by the installation and the default destination folder, which can be changed by using the 'Browse' button. Click 'Next' to continue.
 
-![Cropped screenshot of the Choose Install Location page of the napari EXE installer. A text field next to a Browse button shows the default installation path. Additional text below reports the required space for the installation (2.6 GB) and the total space available on disk (61.1 GB). The three buttons at the bottom read Back, Next and Cancel.](../assets/tutorials/installation/bundle_20.png)
+![Cropped screenshot of the Choose Install Location page of the napari EXE installer. A text field next to a Browse button shows the default installation path. Additional text below reports the required space for the installation (2.6 GB) and the total space available on disk (61.1 GB). The three buttons at the bottom read Back, Next and Cancel.](../../_static/images/bundle_20.png)
 
 On the next page, click 'Install' to start the installation process. Installation progress can be monitored on the following page. By clicking on 'Show details', you can obtain more information on the ongoing tasks. You can right-click on this new text area to copy the contents to the clipboard if needed.
 
-![Cropped screenshot of the Installation process page of the napari EXE installer. A progress bar at around 95% reads "Setting up the package cache...". A button with the text "Show details" is available below. At the bottom of the dialog, three grayed out buttons read Back, Next, and Cancel.](../assets/tutorials/installation/bundle_22.png)
+![Cropped screenshot of the Installation process page of the napari EXE installer. A progress bar at around 95% reads "Setting up the package cache...". A button with the text "Show details" is available below. At the bottom of the dialog, three grayed out buttons read Back, Next, and Cancel.](../../_static/images/bundle_22.png)
 
 Once installation is complete, you will see the page below. Click 'Finish' to close the installation wizard.
 
-![Cropped screenshot of the final page of the napari EXE installer. It reports that the installation has finished successfully and that the dialog can be closed by clicking on the Finish button at the bottom.](../assets/tutorials/installation/bundle_24.png)
+![Cropped screenshot of the final page of the napari EXE installer. It reports that the installation has finished successfully and that the dialog can be closed by clicking on the Finish button at the bottom.](../../_static/images/bundle_24.png)
 
 You can now get started using napari! A shortcut to launch napari can be found in the Windows Start menu.
 
@@ -125,31 +125,31 @@ Next check out our [tutorial on the viewer](viewer.md) or explore any of the pag
 
 Once you have downloaded the Linux SH file, you will have a file with a name like `napari-0.5.0-Linux-x86_64.sh`. Open a new terminal window, navigate to the downloads folder (usually `cd ~/Downloads`) and run the command `bash napari-*-Linux-x86_64.sh`.
 
-![Montage of the SH installer icon on Ubuntu, with an arrow pointing to an open terminal instance with a pre-typed command that reads 'bash napari-0.4.14.dev73-Linux-x86_64.sh'.](../assets/tutorials/installation/bundle_28.png)
+![Montage of the SH installer icon on Ubuntu, with an arrow pointing to an open terminal instance with a pre-typed command that reads 'bash napari-0.4.14.dev73-Linux-x86_64.sh'.](../../_static/images/bundle_28.png)
 
 Press <kbd>Enter</kbd> to display the License Agreement.
 
-![Cropped screenshot of the default Ubuntu terminal displaying the welcome paragraphs of the text-based installer of napari for Linux systems.](../assets/tutorials/installation/bundle_29.png)
+![Cropped screenshot of the default Ubuntu terminal displaying the welcome paragraphs of the text-based installer of napari for Linux systems.](../../_static/images/bundle_29.png)
 
 Read through the agreement shown below. You must agree to the terms by typing out `yes` and pressing <kbd>Enter</kbd> to continue.
 
-![Cropped screenshot of the default Ubuntu terminal displaying the first paragraphs of a BSD-3 Clause License text.](../assets/tutorials/installation/bundle_30.png)
+![Cropped screenshot of the default Ubuntu terminal displaying the first paragraphs of a BSD-3 Clause License text.](../../_static/images/bundle_30.png)
 
-![Cropped screenshot of the default Ubuntu terminal displaying the last paragraphs of a BSD-3 Clause License text, plus a prompt asking 'Do you accept the license terms?', to which the user must respond 'yes' or 'no'.](../assets/tutorials/installation/bundle_31.png)
+![Cropped screenshot of the default Ubuntu terminal displaying the last paragraphs of a BSD-3 Clause License text, plus a prompt asking 'Do you accept the license terms?', to which the user must respond 'yes' or 'no'.](../../_static/images/bundle_31.png)
 
 Next you will be shown the default location for the installation. You may confirm this location by pressing <kbd>Enter</kbd>. Alternatively, specify a different location by typing out its absolute path. If it does not exist, it will be created. The terminal will then begin the installation process.
 
-![Montage of two instances of the default Ubuntu terminal showing the default installation path, followed by the first extraction steps of the installation process.](../assets/tutorials/installation/bundle_32.png)
+![Montage of two instances of the default Ubuntu terminal showing the default installation path, followed by the first extraction steps of the installation process.](../../_static/images/bundle_32.png)
 
 If the installation is successful, the terminal will display a message with the text 'Installation finished'.
 
-![Cropped screenshot of the default Ubuntu terminal displaying the last steps of the installation process. The last line of text reads 'installation finished'.](../assets/tutorials/installation/bundle_33.png)
+![Cropped screenshot of the default Ubuntu terminal displaying the last steps of the installation process. The last line of text reads 'installation finished'.](../../_static/images/bundle_33.png)
 
 You can now get started using napari! A shortcut to launch napari should appear on your desktop or application menu. Under some Linux desktop environments, you can also search for 'napari' using the desktop search bar.
 
-![Full screenshot of the application menu in the Ubuntu desktop environment. A 6x4 grid of application icons includes the napari icon on the third row, third column, highlighted with a red circle.](../assets/tutorials/installation/bundle_34.png)
+![Full screenshot of the application menu in the Ubuntu desktop environment. A 6x4 grid of application icons includes the napari icon on the third row, third column, highlighted with a red circle.](../../_static/images/bundle_34.png)
 
-![Full screenshot of the Ubuntu search menu, with the query 'napari', displaying some results which include the application icon for the installed napari.](../assets/tutorials/installation/bundle_35.png)
+![Full screenshot of the Ubuntu search menu, with the query 'napari', displaying some results which include the application icon for the installed napari.](../../_static/images/bundle_35.png)
 
 napari comes installed with sample images from scikit-image. Use the dropdown menu File > Open Sample > napari to open a sample image, or open one of your own images using File > Open or dragging and dropping your image onto the canvas.
 
diff --git a/docs/tutorials/fundamentals/quick_start.md b/docs/tutorials/fundamentals/quick_start.md
index 0050923b4..671e07524 100644
--- a/docs/tutorials/fundamentals/quick_start.md
+++ b/docs/tutorials/fundamentals/quick_start.md
@@ -109,7 +109,7 @@ For demo purpose, we will use a sample image that comes with napari.
 
 (1) Open napari IPython console
 
-![IPython console](../../images/IPython.png)
+![IPython console](../../_static/images/IPython.png)
 
 (2) Type
 
@@ -206,7 +206,7 @@ viewer.close_all()
 ### Next steps
 - napari provides the flexibility to handle multi-dimensional data. Try opening 3D or higher dimensional images, and switch to 3D view.
 
-![ndisplay](../../images/ndisplay.png)
+![ndisplay](../../_static/images/ndisplay.png)
 
 - Test some [examples](https://github.com/napari/napari/tree/main/examples) to see how to add different layer types and add your own widgets to napari.
 
diff --git a/docs/tutorials/fundamentals/viewer.md b/docs/tutorials/fundamentals/viewer.md
index 0210fb21b..82003f18a 100644
--- a/docs/tutorials/fundamentals/viewer.md
+++ b/docs/tutorials/fundamentals/viewer.md
@@ -76,7 +76,7 @@ nbscreenshot(viewer, alt_text="photograph of an astronaut in napari viewer")
 viewer.close()
 ```
 
- {func}`imshow<napari.imshow>` and the {meth}`add_image<napari.components.ViewerModel.add_image>` methods accept any numpy-array like object as input, including n-dimensional arrays. For more information on adding images to the viewer see the [image layer guide](image-layer).
+ {func}`imshow<napari.imshow>` and the {meth}`add_image<napari.components.ViewerModel.add_image>` methods accept any numpy-array like object as input, including n-dimensional arrays. For more information on adding images to the viewer see the [image layer guide](layers-image).
 
 Now we will continue exploring the rest of the viewer.
 
@@ -100,7 +100,7 @@ The viewer is organized into a few key areas which are explained in the next sec
 
 The image below has the areas of the viewer labeled:
 
-![image: viewer layout](../assets/tutorials/Viewer-with-arrows.png)
+![image: viewer layout](../../_static/images/Viewer-with-arrows.png)
 
 We'll go through each of these in the next sections.
 
@@ -347,7 +347,7 @@ Below the **layer list** is a row containing these buttons:
 * Grid display
 * Home
 
-![image: Viewer buttons](../assets/tutorials/viewer-buttons.png)
+![image: Viewer buttons](../../_static/images/viewer-buttons.png)
 
 Each one is explained below.
 
@@ -362,7 +362,7 @@ The console (when available) appears at the bottom of the viewer as shown below:
 
 +++
 
-![image: console within napari](../assets/tutorials/console.png)
+![image: console within napari](../../_static/images/console.png)
 
 +++
 
@@ -389,7 +389,7 @@ viewer.add_labels(labeled, name='blob ID')
 then, by clicking the 2D/3D button, you can switch to viewing the 3D rendering. Note that the icon will change to
 the following, to indicate 3D mode:
 
-![image: 3D_button](../assets/tutorials/3D_button.png)
+![image: 3D_button](../../_static/images/3D-button.png)
 
 This mode can be entered programmatically using:
 ```python
@@ -427,7 +427,7 @@ will then show you the `ZY` slice. You can also right-click this button to pop-u
 a widget that allows you to re-order the dimensions by drag-and-drop or lock a
 dimension, by clicking on the padlock icon:
 
-![image: roll dimensions widget with padlock icons](../assets/tutorials/dims_roll_lock_widget.png){ w=200px }
+![image: roll dimensions widget with padlock icons](../../_static/images/dims_roll_lock_widget.png){ w=200px }
 
 Locking prevents a dimension from being rolled (reordered). This can be particularly
 useful, for example, with a `3D+time` dataset where you may want to fix the time dimension,
diff --git a/docs/tutorials/processing/dask.md b/docs/tutorials/processing/dask.md
index f5318418b..92b57c1d3 100644
--- a/docs/tutorials/processing/dask.md
+++ b/docs/tutorials/processing/dask.md
@@ -91,7 +91,7 @@ stack.shape  # (nfiles, nz, ny, nx)
 stack
 ```
 
-![HTML representation of a Dask array as seen in Jupyter notebook. The image is split into two main regions: a table showing the bytes, shape, count and data type attributes of the array and of each chunk, and a visual representation of the shape of the chunks that make up the array (a rectangle of 1200x1) and each individual chunk (a 65*256*256 cube).](../assets/tutorials/dask_repr.png)
+![HTML representation of a Dask array as seen in Jupyter notebook. The image is split into two main regions: a table showing the bytes, shape, count and data type attributes of the array and of each chunk, and a visual representation of the shape of the chunks that make up the array (a rectangle of 1200x1) and each individual chunk (a 65*256*256 cube).](../../_static/images/dask_repr.png)
 
 *No data has been read from disk yet!*
 
diff --git a/docs/tutorials/segmentation/annotate_segmentation.md b/docs/tutorials/segmentation/annotate_segmentation.md
index 2aae181fb..edb8bba01 100644
--- a/docs/tutorials/segmentation/annotate_segmentation.md
+++ b/docs/tutorials/segmentation/annotate_segmentation.md
@@ -2,7 +2,7 @@
 
 In this tutorial, we will use napari to view and annotate a segmentation with bounding boxes and text labels. Here we perform a segmentation by setting an intensity threshold with Otsu's method, but this same approach could also be used to visualize the results of other image processing algorithms such as [object detection with neural networks](https://www.tensorflow.org/lite/examples/object_detection/overview).
 
-![napari viewer showing eight roughly circular shapes. The shapes are classified according to circularity and have bounding boxes automatically generated around them showing a circularity parameter and an integer for a label.](../assets/tutorials/annotated_bbox.png)
+![napari viewer showing eight roughly circular shapes. The shapes are classified according to circularity and have bounding boxes automatically generated around them showing a circularity parameter and an integer for a label.](../../_static/images/annotated_bbox.png)
 
 The completed code is shown below and also can be found in the napari examples directory ([`annotate_segmentation_with_text.py`](https://github.com/napari/napari/blob/main/examples/annotate_segmentation_with_text.py)).
 
@@ -139,7 +139,7 @@ napari.run()
 ```
 
 ## Segmentation
-We start by defining a function to perform segmentation of an image based on intensity. Based on the [skimage segmentation example](https://scikit-image.org/docs/stable/auto_examples/applications/plot_thresholding.html), we determine the threshold intensity that separates the foreground and background pixels using [Otsu's method](https://en.wikipedia.org/wiki/Otsu%27s_method). We then perform some cleanup and generate a label image where each discrete region is given a unique integer index.
+We start by defining a function to perform segmentation of an image based on intensity. Based on the [skimage segmentation example](https://scikit-image.org/docs/stable/auto_examples/applications/plot_thresholding_guide.html), we determine the threshold intensity that separates the foreground and background pixels using [Otsu's method](https://en.wikipedia.org/wiki/Otsu%27s_method). We then perform some cleanup and generate a label image where each discrete region is given a unique integer index.
 
 ```python
 def segment(image):
@@ -186,11 +186,11 @@ label_layer = viewer.add_labels(label_image, name='segmentation')
 napari.run()
 ```
 
-![napari viewer showing eight roughly circular shapes, each colored differently. In the left sidebar, the segmentation layer is highlighted.](../assets/tutorials/segmentation_labels.png)
+![napari viewer showing eight roughly circular shapes, each colored differently. In the left sidebar, the segmentation layer is highlighted.](../../_static/images/segmentation_labels.png)
 
 ## Analyzing the segmentation
 
-Next, we use [`regionprops_table`](https://scikit-image.org/docs/dev/api/skimage.measure.html#regionprops-table) from skimage to quantify some parameters of each detection object (e.g., area and perimeter).
+Next, we use [`regionprops_table`](https://scikit-image.org/docs/dev/api/skimage.measure.html#skimage.measure.regionprops_table) from skimage to quantify some parameters of each detection object (e.g., area and perimeter).
 
 ```python
 # create the features dictionary
@@ -315,7 +315,7 @@ Next, we will use the Shapes layer to overlay the bounding boxes for each detect
     )
 ```
 
-![napari viewer showing eight roughly circular shapes, each colored differently. Each shape has a bounding box automatically generated around it.](../assets/tutorials/segmentation_bbox.png)
+![napari viewer showing eight roughly circular shapes, each colored differently. Each shape has a bounding box automatically generated around it.](../../_static/images/segmentation_bbox.png)
 
 The first positional argument (`bbox_rects`) contains the bounding boxes we created above. We specified that the face of each bounding box has no color (`face_color='transparent'`) and the edges of the bounding box are green (`edge_color='green'`). Finally, the name of the layer displayed in the layer list in the napari GUI is `bounding box` (`name='bounding box'`).
 
@@ -405,4 +405,4 @@ napari.run()
 ## Summary
 In this tutorial, we have used napari to view and annotate segmentation results.
 
-![napari viewer showing eight roughly circular shapes. The shapes are classified according to circularity and have bounding boxes automatically generated around them showing a circularity parameter and an integer for a label.](../assets/tutorials/annotated_bbox.png)
+![napari viewer showing eight roughly circular shapes. The shapes are classified according to circularity and have bounding boxes automatically generated around them showing a circularity parameter and an integer for a label.](../../_static/images/annotated_bbox.png)
diff --git a/docs/tutorials/tracking/cell_tracking.md b/docs/tutorials/tracking/cell_tracking.md
index 6706f7608..11c3ac83c 100644
--- a/docs/tutorials/tracking/cell_tracking.md
+++ b/docs/tutorials/tracking/cell_tracking.md
@@ -8,7 +8,7 @@ This application note covers two examples:
 
 ## 1. Cell tracking challenge data
 
-The first example of track visualization uses data from the [cell tracking challenge](http://celltrackingchallenge.net/3d-datasets/). We will use the *C. elegans* developing embryo [dataset](https://data.celltrackingchallenge.net/training-datasets/Fluo-N3DH-CE.zip) which consists of 3D+t volumetric imaging data, manually annotated tracks and cell lineage information.
+The first example of track visualization uses data from the [cell tracking challenge](https://celltrackingchallenge.net/3d-datasets/). We will use the *C. elegans* developing embryo [dataset](https://data.celltrackingchallenge.net/training-datasets/Fluo-N3DH-CE.zip) which consists of 3D+t volumetric imaging data, manually annotated tracks and cell lineage information.
 
 A full description of the data format can be found [here](https://public.celltrackingchallenge.net/documents/Naming%20and%20file%20content%20conventions.pdf).
 
@@ -193,13 +193,13 @@ napari.run()
 
 ## 2. Using `btrack` to track cells
 
-The `btrack` library can be used for cell tracking. It provides a convenient `to_napari()` function to enable rapid visualization of the tracking results. You can learn more about the `btrack` library [here](https://github.com/quantumjot/BayesianTracker).
+The `btrack` library can be used for cell tracking. It provides a convenient `to_napari()` function to enable rapid visualization of the tracking results. You can learn more about the `btrack` library [here](https://github.com/quantumjot/btrack).
 
 ```python
 import btrack
 ```
 
-We start by loading a file containing the centroids of all the found cells in each frame of the source movie. Note that this file only contains the locations of cells in the movie, there are no tracks yet. We can use the `btrack` library to load this file as a list of `objects` that contain information about each found cell, including the TZYX position.  The example dataset can be downloaded [here](https://github.com/quantumjot/BayesianTracker/blob/0f8bbd937535193bde20e3ebe91a323f6bb915e9/examples/napari_example.csv).
+We start by loading a file containing the centroids of all the found cells in each frame of the source movie. Note that this file only contains the locations of cells in the movie, there are no tracks yet. We can use the `btrack` library to load this file as a list of `objects` that contain information about each found cell, including the TZYX position.  The example dataset can be downloaded [here](https://github.com/quantumjot/btrack/blob/0f8bbd937535193bde20e3ebe91a323f6bb915e9/examples/napari_example.csv).
 
 ```python
 objects = btrack.dataio.import_CSV('napari_example.csv')
@@ -226,7 +226,7 @@ with btrack.BayesianTracker() as tracker:
     data, features, graph = tracker.to_napari(ndim=2)
 ```
 
-We set the configuration of the tracker using a configuration file using the `.configure_from_file()` method. An example configuration file can be found [here](https://github.com/quantumjot/BayesianTracker/blob/main/models/cell_config.json).
+We set the configuration of the tracker using a configuration file using the `.configure_from_file()` method. An example configuration file can be found [here](https://github.com/quantumjot/btrack/blob/main/models/cell_config.json).
 
 Next, the objects are linked into tracks using the `.track_interactive()` method. The `step_size` argument specifies how many steps are taken before reporting the tracking statistics. The `.optimize()` method then performs a global optimization on the dataset and creates lineage trees automatically.
 
@@ -238,9 +238,9 @@ viewer.add_tracks(data, features=features, graph=graph)
 napari.run()
 ```
 
-![napari viewer with three layers: an image layer with cells, a points layer with detected cells and a tracks layer with the btrack results. The dimension slider under the canvas is close to the end of the stack, showing the tracks corresponding to each point colored by generation.](../assets/tutorials/tracks_btrack.png)
+![napari viewer with three layers: an image layer with cells, a points layer with detected cells and a tracks layer with the btrack results. The dimension slider under the canvas is close to the end of the stack, showing the tracks corresponding to each point colored by generation.](../../_static/images/tracks_btrack.png)
 
-A notebook for this example can be found in the btrack examples directory ([`napari_btrack.ipynb`](https://github.com/quantumjot/BayesianTracker/blob/caa56fa82330e4b16b5d28150f9b60ed963165c7/examples/napari_btrack.ipynb))
+A notebook for this example can be found in the btrack examples directory ([`napari_btrack.ipynb`](https://github.com/quantumjot/btrack/blob/caa56fa82330e4b16b5d28150f9b60ed963165c7/examples/napari_btrack.ipynb))
 
 ## Summary
 In this application note, we have used napari to track and visualize single cells.
@@ -253,5 +253,5 @@ References for cell tracking challenge:
 + http://dx.doi.org/10.1038/nmeth.4473
 
 For a more advanced example of visualizing cell tracking data with napari, please see the Arboretum plugin for napari:
-+ [btrack](https://github.com/quantumjot/BayesianTracker)
++ [btrack](https://github.com/quantumjot/btrack)
 + [arboretum](https://github.com/lowe-lab-ucl/arboretum)