Skip to content

Hardening candidates: per-language demo GIFs on public surfaces #258

Description

@jeiel85

Follow-ups surfaced while adding the per-language tablet demo GIFs in #257. None block that PR.

  • Landing GIFs ignore prefers-reduced-motion. Six docs/index*.html story-01 figures now animate unconditionally; a GIF cannot be paused by CSS. Swapping to <picture> with a still fallback, or to a muted looping <video> that respects the media query, would let motion-sensitive visitors opt out. Scope: the six landing pages (READMEs are out of reach — GitHub renders them as-is).
  • ~930 KB per landing visit on mobile data. The GIF is loading="lazy", so it does not hit LCP, but a phone visitor scrolling to story 01 still pulls ~930 KB. An animated WebP (roughly a third the size) or a poster-plus-<video> swap would cut that. Scope: docs/assets/, the six landing pages.
  • Nothing verifies that a language page points at its own GIF. README.ko.md referencing markleaf-tablet-en.gif would render fine and ship silently — the same class of gap that verify-landing-versions.ps1 closed for version strings. A check that every index.<lang>.html / README.<lang>.md references markleaf-tablet-<lang>.gif would catch it. Scope: scripts/, wired into the landing-check workflow.
  • markleaf-preview-720/1280.webp are now unreferenced. Kept on purpose (the GitHub Pages URLs may be linked from outside the repo), but nothing records that decision, so a future cleanup will either delete them blind or leave them forever. Scope: decide and note it, or drop them.
  • Demo assets have no version trail. The GIFs were recorded on v2.30.0; when the tablet UI changes, nothing flags that the clips are stale — unlike the landing screenshots, which verify-landing-versions.ps1 pins to a figcaption version. Scope: record the recorded-on version next to the assets, or extend the verify script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions