Private Pro category · 2 compositions
Forms
Longer data-entry and request workflows with complete state handling. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 2 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Account preferences
Category contract
- Purpose
- Longer data-entry and request workflows with complete state handling.
- Declared dependencies
- gummy-field, gummy-input, gummy-textarea, gummy-select, gummy-button
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Forms blocks
Use a longer form composition when the task genuinely requires several related fields or stages. Group questions around the customer’s mental model, mark optional input plainly, and defer information that is not required for the immediate decision or service.
Bind controls to real validation and server outcomes while preserving native semantics, autocomplete, input purpose, error summaries, field-level guidance, and entered values after a recoverable failure. File and sensitive-data handling need explicit limits rather than presentation-only controls.
Test keyboard-only completion, screen-reader announcements, high zoom, slow and offline submission, duplicate requests, expired sessions, invalid files, and provider failure. Confirm retention and consent language with the data owner before any form is connected to production collection.
Document field purpose, data type, validation ownership, sensitivity, retention, authorization, and downstream system for each question. Provide exact errors and recovery behavior, not just a completed visual. The implementation handoff should also identify fields that must never enter analytics, ordinary logs, email notifications, or client-persisted drafts. State how customers correct, export, or delete accepted information after submission. Assign an owner to abandoned and duplicate records as well as completed requests.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.