Be critical of the inputs you place in the primary section, and keep it as short as possible. Make resource creation as easy as possible – having a shorter form to complete both decreases the initial mental load and makes it faster for users to complete your form.
One-click to save
Use good defaults in as many inputs as possible so that users can choose the Create button to have a running resource.
The order of the input fields in the primary section will be re-used as the default table column display, and order.
Validation is performed in two ways:
At the page level when the user triggers the Next button
In most cases, use a single container for all the configuration inputs of a single resource. Consider using multiple containers if the choice is highly complex and would benefit from having its own section in the form layout. Example: Choosing a database type.
Keep the primary configuration section as short as possible. Criteria for primary section inputs:
Any required field that we can’t provide a good default for. Example: password.
Any field that 80% or more of users would expect to see, and want to know the value of in order to be successful. Example: Knowing the security group associated with the resource, even when we provide a good default.
Place as many inputs as possible into the additional settings section for each resource card. This allows the user to keep the primary section as short as possible, so the user can focus on the most important tasks. The label of this section should align with its container's heading, and similarly, should be a noun describing its content, not an action.