I agree. I think that is a good place to start on exceptions for multi-column forms. As time goes on, and products continue to fold in the forms pattern, we may find there are other acceptable cases as well. Starting simple is always a good choice.
On Fri, Sep 23, 2016 at 2:44 AM, SJ Cox <[email protected]> wrote: > Hello UXD and PatternFly community, > > Would love to get your input on when, if ever, multi-column forms are okay. > > This sprint the PatternFly team is working on the conceptual design for > multi column forms. In the case of multi column forms, it’s mostly best > practice to avoid their use. The main problem is that using multiple > columns within forms could cause the potential for users to interpret the > fields inconsistently. > > However, there are a couple exceptions that seem to be acceptable. > > - The main exception for using multi-column forms that cause the least > amount of confusion were strictly for name and address fields. > > > > - The second exception is when there are two different form choices. User > must choose to fill out one or the other. In this case, when the forms > fields are shown next to each other in a multi column format, there is > little confusion as long as the distinction of the two form choices are > clear. > > > > Would love to hear your thoughts and input on this topic. Are there any > other scenarios that are acceptable? Do you agree with the conclusion? > > Thank you!! > SJ > > *Sarah Jane Cox* > User Interaction Designer > User Experience Design Team > > Red Hat, Inc. > <http://www.redhat.com/about/whoisredhat/redhatstories.html?intcmp=70160000000TB9vAAG&;> > >
_______________________________________________ Patternfly mailing list [email protected] https://www.redhat.com/mailman/listinfo/patternfly
