Skip to content

fix(footer): resolve Accessibility/Privacy links at any base path - #31

Open
rancur wants to merge 1 commit into
ArizonaMeshtasticCommunity:mainfrom
rancur:claude/split-01-footer-links
Open

fix(footer): resolve Accessibility/Privacy links at any base path#31
rancur wants to merge 1 commit into
ArizonaMeshtasticCommunity:mainfrom
rancur:claude/split-01-footer-links

Conversation

@rancur

@rancur rancur commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

The Accessibility and Privacy links added in #25 are hardcoded as
/accessibility.html and /privacy.html. Those resolve on azmsh.net but 404 on
any build served from a sub-path, which is every PR preview — so the two pages
that exist specifically for accessibility compliance are the two you can't reach
when reviewing a change.

Moved out of the copyright: string into an override of Material's copyright
partial, which builds them from {{ base_url }}. Also relativized the four
/docs/wismesh-repeater-mini-1w.html links in Recommended Hardware, which have
the same problem.

What to look at: the footer of any page on the preview, then the same page on
the before build — the links
404 there.

Not in this PR: links whose target pages move in PRs 6 and 7.

Preview: https://rancur.github.io/azmsh-site/preview/split-01-footer-links/

The footer links were hardcoded as "/accessibility.html" and
"/privacy.html". Those resolve on azmsh.net but 404 on any build served
from a sub-path, so the a11y/privacy pages added in ArizonaMeshtasticCommunity#25 are unreachable
in PR preview builds.

Move them out of the `copyright:` string into an override of Material's
copyright partial, which builds them from {{ base_url }} so they resolve
at every page depth and under any base path.

Also relativize the five internal links in Recommended Hardware and the
WisMesh build guide that use absolute /docs/*.html paths, for the same
reason.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018pAXdnH4iJEpsWMTYy9hhn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants