shift+home
All checks were successful
beefhavers/ux-manifesto/pipeline/head This commit looks good

I think dantalion has perfect settings?
This commit is contained in:
adam 2025-03-27 17:31:27 -04:00
parent 8c1dad3cb0
commit 6984c00976

View File

@ -225,6 +225,25 @@ Now when you try to migrate between technologies, they do what they can to inhib
[add to rules list] [add to rules list]
don't enclose the commons. don't enclose the commons.
### paradigmatic conformity
You know how a save icon is a floppy disk? A type of storage media so old, I bet if you're listening to this you physically can't use it. But the association has stuck.
You know how on mobile, the menu of all your options is probably 3 parallel, horizontal lines, a.k.a. the hamburger menu? another association that everyone just went with.
[show a screen with a delete button in red, and a screen with a submit button in green]
In life, this extends much further. Red light means stop, green light means go. So when you have an action that could be destructive, you color-code it red, and when something is constructive, you color-code it green.
These associations are abritrary. But since they're there, we keep them.
Can you touch type? imagine I presented you with a blank keyboard. You'd still be able to type, due to a lifetime of training.
Suppose you came across a binder full of papers, and only one of them had a border that was diagonal lines of alternating yellow and black. I can safely assume that you would get the impression that one sheet is providing you cautionary information.
So imagine if I brought up, for example, the discord API documentation, in my web browser. And then I pressed the keypress to get to my search bar. And then your static web page, surprisingly, is an active web app that blocks your web browser's interface to have you use their search function. Surely no one would be that stupid.
right, discord? surely no one would do that. Right? discord? right?
[//TODO: I think i have proper settings on dantalion's FF, because it seems to not be letting shitty web devs break the browser?]
let's look at a pure html static page with a text field. If a user holds shift, and then navigates, they can highlight text. I've seen this far too many times, let's pick on pinterest. if you hit shift+home, that means highlight the whole field. You have to go through effort to break that, and you shouldn't. You don't have a valid reason to do this, rather than nothing.
[add to rules list]
conform to known paradigms.
### wheat from the chaff ### wheat from the chaff
and finally, a short list of features that you know goddamn well no one wants. and finally, a short list of features that you know goddamn well no one wants.