diff options
Diffstat (limited to 'build/proper-ui-hierarchy')
| -rw-r--r-- | build/proper-ui-hierarchy/index.html | 42 |
1 files changed, 2 insertions, 40 deletions
diff --git a/build/proper-ui-hierarchy/index.html b/build/proper-ui-hierarchy/index.html index d3bc682..614b289 100644 --- a/build/proper-ui-hierarchy/index.html +++ b/build/proper-ui-hierarchy/index.html @@ -3,11 +3,12 @@ <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> + <meta name="color-scheme" content="dark light"> <link rel="icon" href="data:,"> <title>Proper UI Hierarchy</title> <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" /> -<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> +<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> </head> <nav> @@ -16,51 +17,30 @@ <main> <h1 id="proper-ui-hierarchy">Proper UI Hierarchy</h1> - <p>2019-02-05</p> - <p>I often feel like an old man when I complain about flat design and how designers these days have lost (or willfully forgotten) the skill to create accessible UIs with proper visual hierarchy. A skill which at it’s core seems so simple - yet is overlooked in almost every current modern interface.</p> - <p>I’m unable to pinpoint the exact reason why designers swapped out depth, hierarchical layouts and accessibility for muted colors, abstract imagery, illegible typography, and unimaginative flat designs.</p> - <p>But then again, maybe I’m just a design-dinosaur of a time long forgotten. Maybe I need to adapt and move with the times. Or maybe the current design trends are just lazy.</p> - <p>I’m pretty sure it’s lazy design trends.</p> - <h2 id="stop-complaining-and-do-something">Stop complaining and do something</h2> - <p>As an example, I’m going to breakdown the process of improving the overall design on a set of “flat” button elements.</p> - <p>Hopefully this demo article inspires even one designer to rethink their method when approaching UI design and push away from what is currently accepted as the “correct way to design UI”.</p> - <p>And one final note before we deep dive into this demo: </p> - <p>The statement that flat design is inherently worse than it’s predecessor <strong>is not subjective</strong>. By stripping away the visual cues that help users distinguish between interface elements you are purposely making a worse experience for them. Designers need to stop designing for other designers.</p> - <h2 id="what-we-will-be-designing">What we will be designing</h2> - <p>In this demo we will be improving the default flat design inspired button layout of the following:</p> - <p><img src="/public/images/proper-ui.png" alt="Proper UI buttons, blue and green" /></p> - <p><a href="https://codepen.io/bradleytaunt/pen/yLXJmdy">Live CodePen Example</a></p> - <hr/> - <h2 id="designing-the-skeleton">Designing the skeleton</h2> - <p>This will be our basic HTML structure, along with it’s default styling (based on today’s UI standards):</p> - <h3 id="the-html">The HTML</h3> - <pre><code><div class="buttons-container"> <button>Sign Up</button> <button>Log in</button> </div> </code></pre> - <h3 id="the-css">The CSS</h3> - <pre><code>/* Parent container for the buttons */ .buttons-container { background: #E0E9EE; @@ -97,23 +77,14 @@ button:last-child { background: #459BCF; } </code></pre> - <h2 id="adding-simple-improvements">Adding simple improvements</h2> - <p>Gradients (not solely on their own mind you) within UI systems were initially used to help humans make connections with their analog counterparts. Something like toggles or switches matching those found in the real world, allowed users to mentally connect what that element’s function did almost instantly. </p> - <p>Be warned not to confuse this with skeuomorphic design - an element sharing similar qualities as it’s analog sibling does not instantly make it so.</p> - <p>If you ever run into a designer who rolls their eyes or scoffs at you for proposing the use of something such as gradients (in a tactful way, of course) it is safe to assume they have been brainwashed by the modern design hive-mind.</p> - <p>To disregard the use of gradients simply because the belief is “gradients are bad” is idiotic. Worse still is to do so based on the belief that “gradients aren’t <em>in</em> right now”. As a designer, your job is to design a beautiful and <em>usable</em> product - not win high-fives among your peers. /end rant.</p> - <h3 id="adding-subtle-gradients">Adding subtle gradients</h3> - <p>When gradients are implemented properly, most users won’t even be aware of their presence. The difference in color (specifically on buttons in this example) helps give the illusion of a light source in the interface, which designers can use to their advantage (ie. pull more attention to elements by “lifting” them forward on the page).</p> - <h3 id="the-subtly-improved-css">The subtly improved CSS</h3> - <pre><code>/* Sign up button */ button:first-child { background-image: linear-gradient(-180deg, #1EB52A 0%, #0D941C 100%); @@ -124,13 +95,9 @@ button:last-child { background-image: linear-gradient(-180deg, #489FD2 0%, #0A6DAC 100%); } </code></pre> - <h2 id="more-depth-light">More depth & light</h2> - <p>With our subtle gradients we are closer to creating a solid contrast between interactive elements, but we can improve this even further. By adding some more depth with a harder light source and more pronounced outlines, we allow the button elements to stand out on their own more strongly.</p> - <p>This is fairly easy to accomplish with CSS using the very basic <code>box-shadow</code>, <code>text-shadow</code> and <code>border</code> properties:</p> - <pre><code>/* Parent container */ .buttons-container { background-image: linear-gradient(0deg, #BBC6CD 3%, #E2EBF0 100%); @@ -157,9 +124,7 @@ button:last-child { box-shadow: 0 1px 5px 0 rgba(9,85,133,0.50), inset 0 -1px 6px 0 rgba(0,0,0,0.20), inset 0 1px 0 0 rgba(255,255,255,0.50), inset 0 2px 4px 0 rgba(255,255,255,0.50); } </code></pre> - <p>For easy reference, here is the CSS styling in it’s entirety:</p> - <pre><code>/* Parent container */ .buttons-container { background-image: linear-gradient(0deg, #BBC6CD 3%, #E2EBF0 100%); @@ -203,11 +168,8 @@ button:last-child { box-shadow: 0 1px 5px 0 rgba(9,85,133,0.50), inset 0 1px 0 0 rgba(255,255,255,0.50), inset 0 2px 4px 0 rgba(255,255,255,0.50); } </code></pre> - <h2 id="going-even-further-with-this-ui">Going even further with this UI</h2> - <p>This demo article only showcases how to improve on a basic button UI structure with a focus on proper hierarchy between elements.</p> - <p>Once completely developed, these element should support all interactive states (<code>hover</code>, <code>active</code>, <code>disabled</code>) and animations to make for a more engaging experience.</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> |