🎨 Palette: Add physical styling to keyboard instructions - #278
Conversation
Added `<kbd>` tags and corresponding CSS to `src/views/mario-game.njk` to highlight keyboard shortcuts ("Space" and "↑"). The custom CSS in the internal `<style>` block provides a physical key appearance with text shadows, improving discoverability and visual distinction against the background. Also logged the UX learning to `.Jules/palette.md`.
Co-authored-by: EiJackGH <172181576+EiJackGH@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Added
<kbd>tags around the "Space" and "↑" instructions in the Mario game view and applied CSS to give them a physical key appearance. Logged the learning in the palette journal.🎯 Why: To improve the intuitiveness and discoverability of custom keyboard controls against a dynamic background, reducing cognitive load for users trying to figure out how to interact with the game.
📸 Before/After: The instructions changed from plain text to visually distinct keyboard keys.
♿ Accessibility: Wrapping keyboard shortcuts in
<kbd>tags improves semantic HTML structure, and the high-contrast physical styling ensures they are readable.Note: Custom CSS was added to the internal
<style>block of the.njkfile because this file does not use utility classes (like Tailwind) and relies entirely on internal vanilla CSS for its styling. This was the only way to adhere to the existing pattern while achieving the necessary styling.PR created automatically by Jules for task 11160904287311225231 started by @EiJackGH