Cloudflare forms
Dense operational forms, validation, and progressive disclosure. All research.
Cloudflare: configuration forms without friction
Cloudflare is useful to Thorbis for form structure rather than visual identity: explicit labels, native semantics, compact technical controls, contextual explanation, and workflows that reveal configuration in the order a person reasons about it. Thorbis keeps Linear's density and its own electric-blue focus language.
- Labels stay visible. Placeholder text can show format or examples, never the field name.
- Size follows the data. Addresses and titles get room; ZIP codes, dates, quantities, IDs, and money remain compact.
- Help lives beside the decision. Short technical explanations belong in the form rather than forcing a trip to documentation.
- Configuration has sequence. Name the thing, define the condition, define the result, then commit or save draft.
- Desktop stays dense. Workbench controls remain 32px; Guided and mobile forms move to 40–44px targets.
- Security stays quiet. Protection should be invisible during normal use and interrupt only when necessary.
Primary sources: Forms, DNS UX, Configuration rules, and Turnstile forms.
Applied bookmark research
Reviewed 2026-09-06. These examples reinforce the existing owners; they do not introduce another visual style or claim the product behavior is implemented. Read the 26-source review and access limits.
A control keeps its meaning through every state
A button that changes width, a field that loses input, or a dialog that loses focus breaks the task even when the resting design looks precise.
Review the approved primitive as a sequence: resting, focused, activated, pending, resolved, and recovered. Keep the action label and footprint stable, associate errors with their fields, and preserve a visible keyboard path.
Thorbis example. Save estimate remains Save estimate while its state mark changes. A validation error keeps the entered values, explains the repair beside the field, and moves focus only when the interaction calls for it.
Verify. Test Tab, Shift-Tab, Enter, Escape where applicable, paste, invalid input, rapid activation, and a slow response. Repeat at 390px, in both themes, with zoom and reduced motion.
Do not import. No hand-built duplicate primitive, hidden label, disabled browser zoom, or borrowed shadow-only outer edge that violates D-017.
Open the ui skill · Evidence: Web Interface Guidelines; Invisible Details; components.build; Details that make interfaces feel better
Transfer the intent, not the desktop gesture
An interaction that works with a precise pointer or modifier key may be unusable for a tech holding a phone.
Preserve the record and task while adapting the visible action path to the device. Use the existing native owner for target sizing, safe areas, focus, and host behavior; no critical action relies only on hover or a hidden gesture.
Thorbis example. A field photo remains attached to the same job when the tech changes orientation or returns from another app. The visible capture action and retry path remain available without discovering a desktop shortcut.
Verify. Check one-handed use, software keyboard opening, text enlargement, orientation, focus visibility, and reduced motion on the relevant device. Keep permission refusal and return-from-interruption states in the review.
Do not import. No desktop hover contract on a phone, blocked zoom, silent clipboard access, or unverified claim that a web imitation is native behavior.
Open the native skill · Evidence: Web Interface Guidelines; Design Engineer Principles; Devouring Details