Repository navigation
Improve the month calendar and page navigation on phones - #282
Merged
Merged
Conversation
On a phone, the month table kept its seven columns, sized in vw, so each day was a 40px cell with 4-7px text. Below 600px it now lays out as one row per day: the date and weekday, then the fast, titles, feasts and saints in readable type, with the whole row still a link. CSS only, so the oEmbed HTML that other sites style themselves is unchanged. Also left-align the readings text on phones, where justifying a narrow column opens wide gaps between words. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 600px the previous/today/next links (and the month links) become full-width buttons at least 44px tall, the tradition and calendar selects fill the row at 44px with 16px text, and the nav uses the full width with a 16px gutter. They were 26px links 4px apart, and 24px selects with 12px text, which iOS Safari zooms the page on when tapped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The title row kept its 75% width while the buttons below it span the screen with a 16px gutter. It now shares that gutter, and the hamburger and its menu end on the same edge. The row's column gap and the nav's negative margin were both 1.5em but at different font sizes, which left the hamburger 3px past the edge, so both are dropped on phones. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A day's readings run to several screens on a phone, so changing days meant scrolling back to the top. Below 600px the readings page now ends with the same previous/today/next buttons; they swap in the new day and scroll to its start. Hidden on wider screens. The content area also takes the 16px gutter on phones instead of 75% of the screen, widening the text from about 280px to 343px on a 390px phone. 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
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.
GoatCounter shows about two thirds of human page views come from phones. Everything here applies below 600px only. It is CSS only apart from the bottom navigation row.
Calendar. On phones the month table kept seven vw-sized columns: 40px cells with 4–7px text. It now becomes a list, one row per day:
The whole row is still a link, and fast days keep their shading.
Day and month navigation.
Readings.
show:window:top). This row is hidden on wider screens. This is the only template change.Scope.
render_calendar_htmlalso feeds the oEmbed API, whose HTML other sites style themselves, so the markup is unchanged.calendar_embed.htmlhas its own inline styles. The weekday names come from the cells'sun…satclasses and are in English, like the header row they replace.Testing. Checked at 390px and 320px: no horizontal scroll. At 320px the "next day" button wraps onto its own row. At 1200px the table and nav are unchanged. All 300 tests pass.
🤖 Generated with Claude Code