When I make a second popover, I often pause over a familiar choice. Should it rise into place like the first one, or simply fade in? If every decision follows the mood of the afternoon, a page soon collects many movements that are almost alike. I want a short vocabulary that gives those choices a reason I can revisit. This sample note uses a fictional project, so the examples are working proposals rather than observations about a released product.
Name what the action explains
The first column in my notebook describes the job of the movement, before mentioning duration. Arrival brings a new state into view. Travel shows that an existing thing has changed position. Departure returns attention to what remains underneath. These ordinary words let me discuss the relationship before choosing distance, direction, or opacity. A conversation about whether a panel belongs beside its trigger is usually easier to follow than a conversation that begins with the name of an easing curve.
Even arrival has several forms. A hint attached to a button only needs to establish a small spatial relationship. A page transition has to help a reader recognize a different location. I do not want those two cases to share a universal preset. I want similar actions to speak with a similar tone, while allowing different amounts of explanation. The vocabulary should reduce arbitrary decisions without turning every component into the same small performance repeated across the page.
Write exceptions beside the rule
This is an arrangement of notes, not a runnable animation configuration. The component still needs to handle focus, cleanup after departure, and a reduced-motion version. Separating the description from implementation helps me notice missing parts of the conversation. We may have spent ten minutes discussing how a panel enters without once asking what happens if someone closes it immediately. That omission matters more than a small disagreement about the final few pixels of travel.
Read several actions together
I open a menu, choose a different option, and close the menu again. Watched as a sequence, the three movements can reveal delays that remain invisible when each component is demonstrated alone. A small pause before every action adds up. An indicator that begins traveling while the menu is still arriving may make it difficult to see which change belongs to which instruction. The useful adjustment is often in the handover between actions, rather than in the duration of one isolated effect.
A quiet movement leaves room for the change that deserves attention.
Departure needs its own pass. After a hint disappears, its trigger is still available. After a panel closes, focus needs a sensible place to return. A visual ending and an operational ending do not always occur at the same moment. Finishing an opacity transition does not prove that the component has restored focus or removed an invisible obstruction. I keep these questions next to the visual description so that the vocabulary remains connected to the way the page is actually used.
The final list is only a few lines long, and I allow those lines to change. When the same exception appears twice, I reconsider whether the category is too broad. A one-off experiment can stay beside its component without becoming a rule for the entire site. What I want to preserve is a shared understanding of why something moves. As the page grows, those simple sentences can support a decision more reliably than a long collection of nearly identical numbers whose original purpose nobody remembers.
