Skip to content

Fix talk entry layout - #3

Merged
p80n-sec merged 1 commit into
mainfrom
fix-talk-layout
Aug 10, 2026
Merged

Fix talk entry layout#3
p80n-sec merged 1 commit into
mainfrom
fix-talk-layout

Conversation

@p80n-sec

Copy link
Copy Markdown
Owner

Reported against the live site: the talks section looked wrong.

What was wrong

Each talk was a two-column grid — title left, event label right — with the abstract spanning both columns but capped at a 68ch reading measure. Since the row was full width and the prose was not, the event label ended up far to the right of where the text stopped, leaving a dead gutter. Each entry read as three disconnected fragments rather than one record.

The slides link also sat 6px below the last line of the abstract, close enough to read as part of the paragraph rather than as a link.

Confirmed it was a design problem and not a deployment one first: the live index.html was byte-identical to the local build.

What changed

CSS only. Each entry is now a single column held to one reading measure:

  • title
  • event byline directly beneath it, left-aligned
  • abstract paragraphs with real spacing between them
  • links, clear of the prose

Also removed the now-dead mobile overrides that only existed to collapse the grid.

Verification

  • 145 tests passing
  • python -m tools.generate --check exits 0
  • Rendered and inspected in both light and dark

🤖 Generated with Claude Code

The two-column grid put the event label at the far right of a full-width
row while the abstract stopped at 68ch, so each talk read as three
disconnected fragments separated by a dead gutter. The slides link also sat
6px under the last line of prose, reading as part of the paragraph.

Each entry is now title, event byline, abstract, then links, held to one
reading measure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@p80n-sec
p80n-sec merged commit 4171b7b into main Aug 10, 2026
1 check passed
@p80n-sec
p80n-sec deleted the fix-talk-layout branch August 24, 2026 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant