From a1f24cf393ebc5874c3195741642a513aa99ff01 Mon Sep 17 00:00:00 2001 From: "google-labs-jules[bot]" <161369871+google-labs-jules[bot]@users.noreply.github.com> Date: Mon, 18 May 2026 13:34:13 +0000 Subject: [PATCH 1/2] =?UTF-8?q?=F0=9F=8E=A8=20Palette:=20Add=20jump=20inst?= =?UTF-8?q?ructions=20and=20score=20a11y=20to=20Mario=20game?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: EiJackGH <172181576+EiJackGH@users.noreply.github.com> --- .Jules/palette.md | 4 ++++ src/views/mario-game.njk | 13 ++++++++++++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/.Jules/palette.md b/.Jules/palette.md index 8ee612f..83f5330 100644 --- a/.Jules/palette.md +++ b/.Jules/palette.md @@ -12,3 +12,7 @@ ## 2025-03-23 - Game Key Scrolling **Learning:** Browsers natively scroll the page when users press Space or Arrow keys. When building a web-based game, this creates a frustrating UX where the game viewport jumps around while playing. **Action:** Always call `e.preventDefault()` on keydown events for typical game controls ("Space", "ArrowUp", etc.) when the focus is on a game container or the body. + +## 2025-03-24 - Explicit Instructions for Custom Interactive Elements +**Learning:** When building interactive HTML5 widgets or games with custom keyboard event bindings, users often don't know the required inputs immediately, causing frustration or abandonment. +**Action:** Always provide explicit, visible instructional text (e.g., "Press Space or Up Arrow to jump!") so users know the required inputs. diff --git a/src/views/mario-game.njk b/src/views/mario-game.njk index 67b6bd7..3e7e34a 100644 --- a/src/views/mario-game.njk +++ b/src/views/mario-game.njk @@ -52,13 +52,24 @@ font-size: 20px; font-family: Arial; } + + #instructions { + position: absolute; + top: 40px; + left: 10px; + color: white; + font-size: 16px; + font-family: Arial; + opacity: 0.8; + }