Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
>It was a push to reduce the number of colors we're using
But is clashes with commonplace UX design principles. Green hints at PROCEED and SUCCESS actions while Blue hints at DEFAULT or PRIMARY actions.
Both Bootstrap and Zurb use similar color schemes for their buttons.
Twitter Bootstrap Buttons
https://v4-alpha.getbootstrap.com/components/buttons/#examples
Zurb Foundation Buttons
https://foundation.zurb.com/sites/docs/v/5.5.3/components/buttons.html#button-colors
In any event I am no fan of conventions. QuickBase should have more affordances to customize styles through partials. A partial is a small fragment of HTML that can carry its own style and content and possibly substitute data into the HTML through a template of some sort. So instead of the interface asking for a single branding color which is hard-coded into the page the interface should asks for a partial - a fragment of HTML that can include styles, images, text content etc.
Users want partials not purple.
But is clashes with commonplace UX design principles. Green hints at PROCEED and SUCCESS actions while Blue hints at DEFAULT or PRIMARY actions.
Both Bootstrap and Zurb use similar color schemes for their buttons.
Twitter Bootstrap Buttons
https://v4-alpha.getbootstrap.com/components/buttons/#examples
Zurb Foundation Buttons
https://foundation.zurb.com/sites/docs/v/5.5.3/components/buttons.html#button-colors
In any event I am no fan of conventions. QuickBase should have more affordances to customize styles through partials. A partial is a small fragment of HTML that can carry its own style and content and possibly substitute data into the HTML through a template of some sort. So instead of the interface asking for a single branding color which is hard-coded into the page the interface should asks for a partial - a fragment of HTML that can include styles, images, text content etc.
Users want partials not purple.