diff --git a/overrides/.upstream/partials/header.html b/overrides/.upstream/partials/header.html
new file mode 100644
index 00000000..2c9b0baa
--- /dev/null
+++ b/overrides/.upstream/partials/header.html
@@ -0,0 +1,69 @@
+{#-
+ This file was automatically generated - do not edit
+-#}
+{% set class = "md-header" %}
+{% if "navigation.tabs.sticky" in features %}
+ {% set class = class ~ " md-header--shadow md-header--lifted" %}
+{% elif "navigation.tabs" not in features %}
+ {% set class = class ~ " md-header--shadow" %}
+{% endif %}
+
+
+ {% if "navigation.tabs.sticky" in features %}
+ {% if "navigation.tabs" in features %}
+ {% include "partials/tabs.html" %}
+ {% endif %}
+ {% endif %}
+
diff --git a/overrides/.upstream/partials/header.html.diff b/overrides/.upstream/partials/header.html.diff
new file mode 100644
index 00000000..57ed37c2
--- /dev/null
+++ b/overrides/.upstream/partials/header.html.diff
@@ -0,0 +1,52 @@
+--- header.html.upstream
++++ header.html
+@@ -1,6 +1,21 @@
+ {#-
+- This file was automatically generated - do not edit
++ Renders the docs header with the mark and the site title both linking to the landing
++ page, the same two controls the landing page's own header carries.
++
++ This is Material's own partials/header.html with two changes. The logo reads
++ landing_root rather than the docs root, and the title block is one link. The block
++ holds both the site name and the page title that replaces it on scroll, so wrapping
++ it leaves one tab stop and the same target whichever of the two is showing.
++
++ The homepage is derived the way the pane's Home row derives it in partials/nav.html,
++ so it follows the deployed root on the custom domain and on the project subpath. On
++ 404.html base_url is a rooted path that may end in a slash, which the replace folds.
++ The theme environment has autoescape off, so every added value carries the e filter.
++
++ The installed partial and the diff to this file live in overrides/.upstream/partials.
++ After editing this file, run: uv run python tools/rederive_overrides.py --record
+ -#}
++{% set landing_root = (base_url ~ '/..') | replace('//..', '/..') %}
+ {% set class = "md-header" %}
+ {% if "navigation.tabs.sticky" in features %}
+ {% set class = class ~ " md-header--shadow md-header--lifted" %}
+@@ -9,7 +24,7 @@
+ {% endif %}
+
+
{% endif %}
diff --git a/overrides/README.md b/overrides/README.md
index 920aef15..dd4070e3 100644
--- a/overrides/README.md
+++ b/overrides/README.md
@@ -1,12 +1,13 @@
# Theme overrides
-MkDocs Material renders any template in this directory in place of its own. Three partials are overridden here.
+MkDocs Material renders any template in this directory in place of its own. Four partials are overridden here.
- `partials/source.html` drops the theme's GitHub API fetch from the header repository link. It is written for this project and tracks no upstream file.
-- `partials/nav.html` is Material's partial with two rows added to the left pane. Home links back to the landing page and opens to its sections. External resources lists the project's outside links. Both rows read `extra.acs_nav` in `mkdocs.yml`, the same block the landing page renderer reads, so the two panes show the same rows.
+- `partials/header.html` is Material's partial with the logo and the site title both linking to the landing page, which is what the landing page's own header does. The target is derived from `base_url`, so it holds on the custom domain and on the project subpath.
+- `partials/nav.html` is Material's partial with two rows added to the left pane and the drawer logo pointed at the landing page. Home links back to the landing page and opens to its sections. External resources lists the project's outside links. Both rows read `extra.acs_nav` in `mkdocs.yml`, the same block the landing page renderer reads, so the two panes show the same rows.
- `partials/nav-item.html` is Material's partial with one change. The current page's link carries `aria-current="page"`, which `docs/stylesheets/extra.css` sets in weight 600 to match the landing page.
-## How the two Material overrides stay reproducible
+## How the three Material overrides stay reproducible
Each Material override is an installed partial plus a small change. `.upstream/partials/` holds a byte copy of the installed partial and the unified diff from that copy to the override. MkDocs skips dot directories, so none of these files is published.
@@ -24,7 +25,7 @@ When Dependabot's checks are green, the partials did not change and its pull req
1. `git switch -c chore/mkdocs-material- origin/integration`
2. `uv lock --upgrade-package mkdocs-material==`
-3. `uv run python tools/rederive_overrides.py` and read the delta it prints. That is everything upstream changed in the two partials.
+3. `uv run python tools/rederive_overrides.py` and read the delta it prints. That is everything upstream changed in the three partials.
4. `uv run python tools/rederive_overrides.py --accept-delta `
5. `uv run pytest -q`
6. `gh pr create --base integration`
diff --git a/overrides/partials/header.html b/overrides/partials/header.html
new file mode 100644
index 00000000..fef8cdd9
--- /dev/null
+++ b/overrides/partials/header.html
@@ -0,0 +1,84 @@
+{#-
+ Renders the docs header with the mark and the site title both linking to the landing
+ page, the same two controls the landing page's own header carries.
+
+ This is Material's own partials/header.html with two changes. The logo reads
+ landing_root rather than the docs root, and the title block is one link. The block
+ holds both the site name and the page title that replaces it on scroll, so wrapping
+ it leaves one tab stop and the same target whichever of the two is showing.
+
+ The homepage is derived the way the pane's Home row derives it in partials/nav.html,
+ so it follows the deployed root on the custom domain and on the project subpath. On
+ 404.html base_url is a rooted path that may end in a slash, which the replace folds.
+ The theme environment has autoescape off, so every added value carries the e filter.
+
+ The installed partial and the diff to this file live in overrides/.upstream/partials.
+ After editing this file, run: uv run python tools/rederive_overrides.py --record
+-#}
+{% set landing_root = (base_url ~ '/..') | replace('//..', '/..') %}
+{% set class = "md-header" %}
+{% if "navigation.tabs.sticky" in features %}
+ {% set class = class ~ " md-header--shadow md-header--lifted" %}
+{% elif "navigation.tabs" not in features %}
+ {% set class = class ~ " md-header--shadow" %}
+{% endif %}
+
+
+ {% if "navigation.tabs.sticky" in features %}
+ {% if "navigation.tabs" in features %}
+ {% include "partials/tabs.html" %}
+ {% endif %}
+ {% endif %}
+
diff --git a/overrides/partials/nav.html b/overrides/partials/nav.html
index bd0b3a8f..f154ce5c 100644
--- a/overrides/partials/nav.html
+++ b/overrides/partials/nav.html
@@ -1,7 +1,8 @@
{#-
Renders the docs site's left pane with the same rows as the landing page's pane.
- This is Material's own partials/nav.html with two rows added around the stock loop.
+ This is Material's own partials/nav.html with two rows added around the stock loop
+ and the drawer logo pointed at the landing page, as the header's logo is.
Home links back to the landing page and opens to its sections. External resources
lists the project's outside links. Both read config.extra.acs_nav in mkdocs.yml, the
one source the landing renderer reads too, so the two panes cannot drift apart.
@@ -30,7 +31,7 @@
{% set landing_root = (base_url ~ '/..') | replace('//..', '/..') %}
- ACS
-
-
-