Repository navigation
feat(docs): link the translations under the breadcrumbs, and the AI notice before the footer - #545
Merged
Merged
Conversation
…the article Neither landed on the published site, and the live page said why. The header can finish rendering between the check for it and the observer armed when the check fails, and then no mutation ever follows to react to — so the controls stayed at the bottom of the viewport. The observer is still there for the common case, but a poll every 150ms now closes that gap, with one deadline to stop both. The notice was inserted before </body>, where the application's own layout places it at the top of the page rather than after the text. It goes inside the article now, as its last paragraph, and falls back to the end of the body only where a page has no article. Refs #539
… at the end that AI wrote this The floating pair is gone: no language button, no search button, and with them the widget, its script and the profile entry that pointed at it. Two plain blocks take their place, written into every built page and needing no JavaScript at all — a reader without it, and a crawler that runs none, see both: - a row of links at the top of the article, which is directly under the breadcrumbs, carrying the same page in the other four languages, the current one named but not linked; - the notice at the end of the article, above the footer, in that page's language. The assembled job checks for those two instead of the controls it used to. Refs #539
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The floating controls are gone — no language button, no search button — and with them the widget, its script and the build-profile entry that pointed at it.
Two plain blocks replace them, written into every built page, needing no JavaScript, so a reader without it and a crawler that runs none both see them:
finalize-site.mjswrites both, as it already writes thehreflanglinks, the canonical link and the structured data — the build profile is not applied on this builder, which is what theassembledjob now guards against, checking for these two blocks instead of the controls it used to.How to test
The
assembledjob assembles the five builds as the deploy does and checks three pages for the language row, the notice, the canonical link and the structured data.Related issues
refs #539
🤖 Generated with Claude Code