Skip to content

Fix: correct the Language setting location and restore in-page navigation - #14

Merged
SandObserver merged 2 commits into
mainfrom
fix/settings-language-and-page-toc
Aug 24, 2026
Merged

SandObserver merged 2 commits into
mainfrom
fix/settings-language-and-page-toc

Conversation

@SandObserver

@SandObserver SandObserver commented Aug 24, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Move Language from Appearance to General in the first-setup section table, matching where the setting is rendered in the app.
  • Add a Language group to the Settings Reference General section, which previously omitted the setting entirely.
  • Document SESSION_MAX_AGE_DAYS as a 0.5 day default instead of 12h, so the value matches the units the variable parses.
  • Add withHeadingIds and slugify to src/lib/repo.ts, which assign ids to headings in the HTML marked produces and return the heading list.
  • Pass those headings to StarlightPage on the accessibility and development pages, which rendered an empty table of contents and no anchor targets.
  • Build a release-level table of contents for the changelog, give each release an id, and drop tableOfContents: false.
  • Open the targeted <details> on load and on hashchange, so a changelog release linked from the table of contents scrolls into view.
  • Add a setting check to scripts/check-dist.mjs comparing the admin UI row labels against the Settings Reference table, warning on anything undocumented. It skips without an app checkout and never fails the run.

Testing
All green: npm run build and npm run check both pass. Verified the new setting check reports the missing Language row against the pre-change reference, reports nothing after it, and skips cleanly with STACKYARD_REPO pointing nowhere.

Checklist

  • npm run build and npm run check both pass.
  • Product UI is shown by running or capturing it, never recreated in CSS.
  • Any new preview or screenshot carries no private hostnames or real data.
  • Visual changes verified in both colour schemes and both docs themes.
  • Links to the app repo still resolve.

Replace the Google Fonts stylesheet with a self-hosted Latin subset of
the Inter variable font, preloaded on every page.

Point the landing page and the documentation theme at one family for
both headings and body text. The documentation heading font previously
resolved to a face no page loaded.

Swap the header brand from an icon plus live text to the wordmark, dark
only on the landing page and per theme in the documentation header.

Extend the build gate to verify font assets ship.
Correct the first-setup section table to place Language under General, and
add a Language row to the Settings Reference General section.

Document SESSION_MAX_AGE_DAYS with a numeric day default instead of a
duration string.

Add heading ids and a table of contents to the pages generated from
repository files.
@SandObserver SandObserver added documentation Improvements or additions to documentation content Documentation content: wording, structure, new pages labels Aug 24, 2026
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying stackyard-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a21e2ef
Status: ✅  Deploy successful!
Preview URL: https://97ab5db4.stackyard-docs.pages.dev
Branch Preview URL: https://fix-settings-language-and-pa.stackyard-docs.pages.dev

View logs

@SandObserver
SandObserver merged commit 73f8d91 into main Aug 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content Documentation content: wording, structure, new pages documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant