Repository navigation
Docs: new theme in the TTN 2026 design, shared cookie consent, CI on ubuntu-22.04 (merge at the www cutover) - #561
Merged
Merged
Conversation
New Hugo theme built from the Claude Design "LoRaWAN Docs" design: global TTN header/footer from the platform's single nav source (data/site_nav.json, root-relative + params.ttnOrigin), sidebar navigation, chapter cards, on-this-page rail, search, callouts, prev/next. Header geometry is identical to the www header (platform site.css). Replaces the Bulma/SCSS theme and drops the Node/Yarn asset step from CI. DO NOT MERGE before the thethingsnetwork.org cutover: merging to master publishes to GitHub Pages, which the live site serves at /docs today. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Regenerated doc/data/site_nav.json from platform/app/lib/site-nav.ts with platform/scripts/export-docs-chrome.mjs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The lorawan page sets `image: /lorawan/icon.png`; relURL keeps a leading slash at the host root, so the card asked for /lorawan/icon.png and lost the /docs/ base path (404). Trim the slash before relURL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… www /consent.js) The hard-coded GTM snippet (and its noscript iframe) loaded GTM-PP5G5BT for every visitor, with a "Got it" notice shown only in European time zones. Replaced by the www platform's /consent.js (thethingsnetwork-v2 platform/app/lib/consent-script.ts): a real consent banner, GTM injected only after "Accept", one choice for the whole www origin (site, docs, device repository). - head: <script src="/consent.js" defer> — root-relative, so only behind the www front door; the raw GitHub Pages origin and local Hugo previews stay untracked - baseof: GTM noscript iframe and the old cookie-notice partial removed (partial, JS and CSS deleted) - footer: "Cookie settings" control (hidden until /consent.js reveals it) to change the choice - data/site_nav.json re-exported (footer gained "Help & user guide") Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n versions The release and pull-request workflows were pinned to ubuntu-20.04, which GitHub no longer schedules, so a push to master would never deploy. Same toolchain (Go 1.17 → Hugo 0.88.1, Node 16); checkout/setup-go/cache/ setup-node bumped to current majors, and the gh-pages deploy action to v4 with clean: false (v3's behaviour) and an explicit contents: write. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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 docs in the new The Things Network 2026 design, for the www.thethingsnetwork.org cutover. Merging to
masterdeploys to the livegh-pagessite, which serves www.thethingsnetwork.org/docs.Changes
site-nav.tsin the new platform), so/docsmatches the rest of www./get-started./consent.js. It replaces the hard-coded GTM snippet.ubuntu-20.04, which GitHub no longer runs, so a push tomasterwould never deploy. They now useubuntu-22.04and current action versions, with the same toolchain (Go 1.17 → Hugo 0.88.1, Node 16). The gh-pages deploy action moves to v4 withclean: false, matching v3's behaviour.Notes for reviewers
/get-started). Those only exist once www points at the new site, so merge at the DNS flip, not before.🤖 Generated with Claude Code