alt Hacker NewsAt work we call this implicit steering. To use webdev metaphor, if a non-technical person describes making a web page with a big block at the top and some things to click on and then my pictures below that, that will eventually get somewhere. Meanwhile, if you know industry jargon, you might describe a hero, with call to action buttons, and then below a 3x3 grid of images of my portfolio photos—that's likely going to generate something entirely different and likely richer. It can assume things about you (it doesn't think), it can ask you specific questions a web personal might know, it can infer domain context that is otherwise omitted with a basic conversation. Everyone wants to capitalize on corporate vibe coding but the tech literacy is hardly there, let alone more advanced topics.
Opus, assume i know nothing about web development. if i wanted to design a new webpage, with a good design, what are some of the terms of art, some best practices? Like if i wanted a big block at the top, some things to click on and some pictures below that, is there terminology for that?
>Yes. Nearly everything you described has a standard name. Here is the vocabulary, organized by what part of the page it describes...
Goes on to identify Header, Navbar, Stucky header, hamburger menu, hero, CTA, Above the fold etc.
>So your described page is: header/nav -> hero with CTA -> card grid -> footer. That is the single most common landing page structure in existence, and that is fine. Being conventional is a feature, not a failure.
I've had the same conversation with an electrician wiring a car charger: we are more likely to succeed if I use his terminology.