Design Principle
Good forms split complex tasks into completeable steps rather than dumping every field at once.
Principle
Good forms split complex tasks into completeable steps rather than dumping every field at once.
Design action
Group fields by basics, body, agent directive, and publishing settings; save draft and submit for review should use different button priorities.
Examples
Positive example: Knowledge submission, asset upload, account settings, and payment. Counterexample: After submission fails, users do not know what to fix.
Apply when
Knowledge submission, asset upload, account settings, and payment. More than six fields or review states exist.
Source notes
Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles. Apple HIG Motion: https://developer.apple.com/design/human-interface-guidelines/motion Material Design Motion: https://m3.material.io/styles/motion/overview/how-it-works GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Shopify Polaris Patterns: https://polaris-react.shopify.com/patterns Atlassian Empty State: https://atlassian.design/components/empty-state
Agent Directive
Group fields by basics, body, agent directive, and publishing settings; save draft and submit for review should use different button priorities.