Return to English Documentation Index · Choose Language · Browse Files

UI Behavior

The interface should feel calm, orderly, visually clear, and predictable. Established behavior should not shift casually between builds.

Documentation should explain behavior in human terms so readers understand what to expect before using the app.

2026-03-17 Conversation Additions

2026-03-17 Additive Expansion: The UI now has explicit behavior requirements derived from the conversation and the schools-worldwide deployment goal.

A. Controls and Labels Localization Rule

All user-facing controls, labels, menus, toggles, and messages must be documented as localizable. No control may be permanently locked to English-only text in the canonical system design.

Use language-agnostic keys or another documented localization mechanism.
Longer translations must not break the UI.
LTR and RTL layouts must be considered in control positioning and spacing.
Label rendering quality must remain sharp at target export sizes where labels appear in outputs.

B. Live / Export Parity Expectation

When a user sees a QR, type pill, URL-art arrangement, header toggle state, or footer behavior live, the exported result should honor the same visible decisions unless a separately documented export exception exists.

C. Controls Mentioned in Conversation

Grid slider behavior and related grid fitting must not regress.
Fit Height and Fit Everything behaviors must remain correct and deterministic.
Header text toggle must remain functional.
Uploaded thumbnail contain-mode behavior must remain preserved where specified.