Skip to content

Let the detail view follow the picture's format #28

Description

@nordfisch

A landscape picture needs width and has height to spare — the text belongs below it. A portrait
picture needs height and has width to spare — there the text belongs beside it, as it does
today. The view knows which it is showing: the picture carries its aspect ratio as aspect-ratio
(frontend/src/kiosk/PhotoOverlay.tsx), and .overlay__content is a two-column grid that could
switch to one.

The collection says it is worth doing. Counted on 8 September 2026 over the 1279 published
photos: 1177 landscape against 100 portrait, and 2 square.

That is also why it is not done in passing. The change touches almost every photo in the
collection, and whether it looks better is decided on a device in a room, not in a browser window.

Three pragmatic parts of this were fixed on 16 August 2026 and are not part of this item any
more: the text column grows instead of standing fixed (at 1024 px the picture gets 610 px instead
of 466), the paging buttons sit at the bottom edge, and the close button sits in the corner of the
screen. See
decisions.md,
point 44.

This waits on #20, and it really does wait. If the device ends up portrait, the reasoning
reverses and the change would have to go the other way. Until the screen is decided, every number
here is an assumption.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ideaNot yet decided whether at allvisitorArea: the visitor view at the kiosk

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions