Reader: wider article images with configurable card space #22
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Article images use only a fraction of the card width in the reader, wasting horizontal space.
Goal
Findings
style.css, which is already variable-driven — the image width should become a variable rather than a hardcoded value so the configurable part is trivial.Plan of attack
Updated plan
The display-settings mechanism from #8 has landed, so configurability follows that pattern directly.
Approach
:rootgains--aggregate-image-width: 100%and.aggregate-imageuseswidth: var(--aggregate-image-width)instead of the hardcoded100pxsquare. Height becomesaspect-ratio: 3 / 2with amax-heightcap so any configured width keeps a sensible shape (object-fit: covercrops). Default100%satisfies "at least twice as wide" — cards are ~half the main column, so the old 100px was under 20% of the card width. The mobile override already forces full width and needs no change.image_widthdisplay setting — text input in the Display section of the settings page, validated with the same CSS-size pattern as font size (px|rem|%, case-insensitive), empty = default.base.htmlemits:root { --aggregate-image-width: <value>; }when set, exactly like font size.Branch
feat/issue-22-wider-card-imagesCommits
:sparkles: Widen card images via an --aggregate-image-width variable:sparkles: Add card image width display settingTDD: failing tests first (setting save/reject/case-insensitive units, form persistence, default leaves the inline override absent, stylesheet uses the variable), then implementation, then full
noxbefore push.Implemented in PR #30 (merged as
2c0e562): card images render via--aggregate-image-width(default100%,3/2aspect, 240px cap), configurable through Settings → Display → Card image width.