Content
Quick reference
| Use Case | Page | Side Panel | Modal Window |
|---|---|---|---|
| Process complexity | High | Low to medium | Very low (single action) |
| Need for page context | No | Yes | No |
| Form input length/detail | Long or complex | Short or moderate | Very short or single field |
| User attention required | High | Medium | High (briefly) |
| Best for | Full creation flows, settings | Inline creation, quick edits | Confirmations, warnings, deletions |
| Avoid for | Simple edits or confirmations | Long, multi-step processes | Full forms or complex interactions |
Pages
Use a dedicated page when the form involves a complex, multi-step process that requires significant user attention and multiple Input or interactions. Pages are appropriate when the content cannot be comfortably contained within a side panel, and when the user does not need to retain context from the previous screen. For example, creating or managing an item independently of where it will eventually appear.
Side panels
Use a side panel when maintaining context from the current page is important. If the user is performing a task directly related to the content or structure of the current page, such as creating a sub-item or editing an inline component. The side panel allows them to maintain that relationship without disruption. Side panels work best for lightweight or medium-complexity forms where having the surrounding information visible enhances the user's understanding or efficiency.
Modal windows
Modal windows should generally not be used for forms. Since modals interrupt user flow and demand focus, they are better suited for confirmation dialogs, warnings, or critical decisions, particularly destructive actions that may involve a confirmation Input (such as typing "DELETE" to confirm an irreversible operation). Modals should not be used as a shortcut for tasks that are better suited to a full page or a contextual side panel.