Frontend modernization#81
Merged
Merged
Conversation
Move the UI to 2026 CSS standards and remove the sassc toolchain. - Typography: self-host Literata variable font (latin subset, roman + italic) for long-form reading; UI chrome stays system-ui. - Theming: oklch palette with light-dark() and a manual auto/light/dark toggle persisted in localStorage; FOUC-prevention bootstrap in <head>. - CSS: rewrite around @layer (reset, tokens, base, components, pages), logical properties, container queries, fluid type via clamp(), cross- document view transitions, native CSS nesting. Ship each partial as its own .css file under web/dist/css/ and link them all from base.hbs — no compile step, no @import waterfall, layers.css sets cascade order first. Removes the sassc apt install and SCSS compile from Dockerfile. - HTML: pull header chrome (logo, search, theme toggle) into base.hbs; verses become an <ol>/<li> with a gutter for verse numbers and a two-line drop cap on v1; <link rel=prev/next> emitted in <head>. - JSON-LD: fix WebSite casing, remove the nested @context inside breadcrumbs, add SearchAction WebSite for the home page, SearchResultsPage on /search, AboutPage on /about. - JS: drop the unconditional preventDefault on the search form (works without JS now); switch swipe nav to Pointer Events; replace document.onkeypress with addEventListener('keydown'); publish header height as --header-h so the autocomplete dropdown can anchor itself below the sticky header; service worker bumped to v7 with a network-first / SWR routing split and the new CSS files precached. - Misc: scoped Cache-Control immutable on /static/fonts/*; BIND_ADDR env var for local dev; remove a stray println! from link.rs.
The pointer-based swipe handler fought iOS Safari's edge-swipe-back gesture and was an undiscoverable duplicate of the existing prev/next chrome in .page-nav and .chapter-tools. Drop it along with the now-unused link-prev/link-next ids; the <link rel="prev/next"> tags themselves stay for browser prefetch and crawler hints.
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.
No description provided.