-
Notifications
You must be signed in to change notification settings - Fork 26
Form Input inventory #733
Comments
Form inputs for v2.0 and their usage
|
@denisewildner @jeannewalters Note: This issue is only to collect the different types. UX and Visuals will be treated in separate issues. |
I created an Invision board to collect examples of existing UIs — and added a Forms section. We should gather examples from EC as well. https://sapse.invisionapp.com/d/main#/projects/boards/5484242 We should not be posting screen shots of our products publicly. |
Not posting is products screenshots is, of course a must, but links to protected wiki pages it will be fine. We can also avoid that and only post small screenshots of individual elements. |
With the Elements created on #735 and the types on #733 (comment) and looking at the uses cases from #733 (comment) Inputs types with common elements
|
This is done |
Reopening this to keep it in context Action and Action + Icon: Since the Icon + Action have a accent color (blue), I think we can give the Action and the Action + Icon the same color to keep it consistent Read only: is missing the border. |
The colors aren't completely flushed out here. I made them black as placeholder. But in theory yes they will probably be a grey shade or the action blue from the color palette. Jeanne and Irla are still having UX talks about how the fields should look. They were supposed to talk today to finalize. |
Goal: have in inventory of at most input line uses cases.
The form inputs Current cases we have now:
https://techne.yaas.io/components/Form-Elements.html
Note: Not to be confused with "states" of the input field like: pristine, error, focused, etc.
The text was updated successfully, but these errors were encountered: