oh oi, we've called these "infopops" because "cards" means a lot in the ui world and also because lolipops are fun
commit b199b7be646fe2f51f39194cb36dbad75b7461fb · parent 5377260618
· browse this tree
warpfork, 2026-10-10 02:39:37 UTC
diff --git a/docs/precepts-we-love-the-keyboard.md b/docs/precepts-we-love-the-keyboard.md index cdc65cf..0bf5d26 100644 --- a/docs/precepts-we-love-the-keyboard.md +++ b/docs/precepts-we-love-the-keyboard.md @@ -111,7 +111,7 @@ But text entry dominates: if we're doing text entry, then that's what we're doin and the space key is for inserting spaces. -### info cards +### info pops One norm that Yukey standardizes, specifically to counter the "mouse has tooltips, keyboard has whoops" problem: @@ -121,7 +121,7 @@ and also many that are purely informative: the hotkey `?` means "info, please", and does something similar to raising up a tooltip. -#### what goes in info cards? +#### what goes in info pops? User's choice. @@ -131,12 +131,12 @@ or a whole... anything. But broadly, it should probably be on the short end of the range. -#### what *doesn't* go in info cards? +#### what *doesn't* go in info pops? -An info card should used for novel details about the element in question, +An info pop should used for novel details about the element in question, not reiterations of general interaction guides. -For example, an info card should not: +For example, an info pop should not: - **Name hotkeys.** Yukey has a whole visual language for that already. - **Describe global norms.** E.g. it makes no sense to describe what Escape does, nor what arrows do. @@ -144,7 +144,7 @@ For example, an info card should not: - **Describe what Enter/activation does in generic terms.** Enter is activate. This falls under the same admonition against describing global norms, but further: As a UX story in your application, if what activation of an element will do isn't clear, - then explaining it in the info card isn't the right place: a clearer label should be used, + then explaining it in the info pop isn't the right place: a clearer label should be used, or the button is simply too dangerous -- fix that; don't try to hide warnings in the lower-visibility margin notes! - **Narrate what focus or hover does.** By the time the tooltip is open, focus or hover already happened. Describing what already happened would make no sense.