1

Do you have any design-related questions or suggestions? We'd love to hear from you.

Please contact Wuiman to discuss your ideas.

John Doe

Form Elements

Summary

Here you will find a collection of different form elements. All elements are displayed as if they were in a panel with reduced width. The different form elements are divided into 5 main sections:

  • Basic. Many say exploration is part of our destiny, but it’s actually.
  • Extended. To explore strange new worlds, to seek out new life and new
  • Tupels. New worlds, to seek out new life and new civilizations
  • Advanced. Many say exploration is part of our destiny, but it’s actually.
  • Selectables. To explore strange new worlds, to scivilizations

Draft

This page is WIP. Things are very likely to change in the future. So please do not use these elements in production yet. But we are always happy if you help us to build the elements in the best possible way. If you have any suggestions for improvements, if you find a bug or if you have anything important which should be included in the documentation, feel free to contact me via slack, email (tjaeger@wescale.com) or personally.

General guidelines

  • Check if it makes sense to set the first form-control of the page to autofocus.
  • A label and a form control should be associated with each explicitly. Therefore the for attribute of the label must exactly match the id of the form-control.
  • Use the right "tpye" for your input
  • All listed form elements are shown as if they were on a medium sized screen. As a rule of thumb: On large screens the bs-col-size of input elements is always summed up to 6. On medium screens (and smaller) the bs-col-size is always summed up to 8.

Basic form elements

  • Disabled vs. readonly. Even if they look the same there is a difference between these two inputs. The contents of a read-only input can - for example - be selected with the mouse and then copied. The input is also part of the tab index of the page. Whereas the content of the disabled input cannot be selected at all.
  • Textarea To indicate to the user that a complete text can be entered in this field, the text area should be large enough and have a row attribute of 3 by default.

Extended form elements

For some fields it can be useful to validate them asynchronously. For example, we use this input field to check the uniqueness of a name, so that the user gets feedback on the entry even before the update button is clicked.

  • The addon of a form-group is (like the label) explicitly connected to the input
  • When you have multiple addons grouped in one form-group the addons should have all the same length.
  • Within an input group addon there can be optional and required labels. But as soon as one label is required, the main label is required as well.

Form examples

Full width


Navigation

Panel next to subnavigation


Panel next to widget

Widget


Form Generator split