The law of this section. Every time Frank corrects or approves, a numbered criterion is added here, with the why.
Show, don't label
A concept card with an abstract label ("a person, melted in") tells Frank nothing. Every concept carries a real example: a screenshot, a thumbnail, a named site with its picture. He judges "is this what I want?" on sight, not on a caption.
Why. These pages exist to be understood fast and acted on. Words that don't serve that are eliminated.
No unexplained jargon, ever
A technical name like GSAP or Three.js either earns a one-line plain explanation, or it does not appear.
Why. "I have no idea what GSAP is, so either you explain if it is worth it, or you don't mention."
Every element earns its place, or goes
A card whose purpose is not clear on sight is deleted, not decorated.
Why. "Whatever doesn't convey any clear meaning should be eliminated."
Everything Frank reads here is an HTML page
Markdown stays only as the machine source. Every index and back-link points at the HTML view.
Why. "I see that you still write documents in md for the UI/UX document. They all should be in HTML."
Sibling controls are twins
Neighboring controls share one component, one container, one baseline. Screenshot every UI state and check each pair of neighbors before delivering; prefer discreet twin icon buttons over text pills.
Why. "Two different sizes of buttons, not aligned: you should never produce something like this." Global rule: feedback_html_output_rules.md §26.
A person in a page introduces herself with a card
Beside the person, a white card: "Hola, soy [name]", one short question, ONE primary action in the accent color ("Sí, escuchar") and one quiet text alternative ("Conversar"). The card hides while she speaks and returns when she stops.
Why. "This is the card I like", chosen over icon pairs: with only two actions, plain words beat symbols that need decoding. Live example: Valentina.
A card leads to an introduction, never to a raw source
Every card on the Studio front page opens a page that introduces its subject plainly: what we do with it, the real examples, the tools, the method. If that page does not exist, build it before shipping the card.
Why. The Voice card opened a French leaflet about trader status. "One expects an introduction to the topic, very simply, what do we do with voice."
The word is speaker; the sizes are settled
The person on a page is a speaker, never "talking bust". Its forms are sizes: face · half bust · bust · full body. Every size speaks; a still picture is the separate option before the speaker. Two kinds, always distinguished: the still speaker (speaks, does not move — Zalia, Grace; almost free) and the moving speaker (speaks and moves — Valentina; master clip + centimes per part). The still one stays on offer because it is cheaper and quicker.
Why. "If it is a speaker, just say speaker." · "I don't know what rungs is." · "What is new now is that it is a moving, animated speaker. Let's show the distinction clearly."
An illustration shows one thing only
An image that illustrates the speaker contains only the speaker — no unrelated buttons or controls in the frame, and never a control that no longer exists on the live page.
Why. "You make people think that you have two buttons… this is not the case. Don't mix the problems."
Studio pages: concise, visual, collapsible
As concise as possible. An image wherever it can replace text. Every section collapsible.
Why. "Less text and more visual presentation" · "Make sections collapsible… Same for the other sections."
Features are presenting vs talking
The speaker has two features: presenting (she reads the page part by part — works today) and talking (a real conversation — not ready; its button stays off the page until it is). A page about the speaker shows the real button, and the real icons that appear after the click.
Why. "Stay for the time being on the presenter. Talking, we don't know how to do it yet."
A Studio page is a cookbook
Titles name dishes ("Make pages move", "Use video, not code"), sections are recipes — what you get, what you need, the steps, the cost, where it is proven — and no words about ourselves: no "doctrine", no manifesto register, no essay sentences.
Why. "This is a practical manual, not a report nor a manifest… our model is a cook book, should be all very concrete."