Hey there! Brian Dys here — I’m a visual and visceral person at heart. Ever since my mom lent me her old film camera, I fell in love with photography. All of my creative musings were exemplified by my second brain, the computer. This journey is a topsy-turvy ride of creative pursuits — from electronic music to UX design.
I enjoy every dull and wild moments of it — yes, this life of mine that I share with a woman named Jaycelle and a boy named Bryce. Take a peek into my kaleidoscope!
http://web.archive.org/web/20070416110618/http://www.cmsreview.com:80/IA/glossary.html
http://web.archive.org/web/20060831192727/http://www.cmscalendar.com:80/ia-glossary.html?term=Taxonomy
http://web.archive.org/web/20070408112138/http://www.bobgoodman.net:80/main/glossary.html
http://web.archive.org/web/20070220214703/http://www.theusabilitycompany.com:80/resources/glossary.html
http://web.archive.org/web/20070417104203/http://www.iawiki.net/action=browse&id=GlossaryOfTerms&oldid=IAGlossary
http://web.archive.org/web/20070415101307/http://www.jnd.org:80/dn.mss/affordance_conventi.html
http://web.archive.org/web/20070427045700/http://www.usabilityfirst.com:80/glossary/main.cgi
http://web.archive.org/web/20070501121141/http://www.iawiki.net:80/DeliverablesAndArtifacts
https://docs.google.com/spreadsheets/d/1h2hyR1S9v_Pgv64jmNexebAIIXGQqdB58mI6TDSDzng/edit#gid=0
https://docs.google.com/spreadsheets/d/1dQMHXzwG9q3eqX8hdVKKjDCIQux7pjZM9um4lEB3yss/edit#gid=0
https://www.ischool.utexas.edu/~i385e/readings/Warner-aTaxonomyPrimer.html
We need to incorporate the possibility of moving up the employment level by breadth—encompassing the other disciplines and depth—by fulfilling the Work Efficiency Responsibility needed for the next level.
We need to fill-in the details—criteria also—for moving across and moving up. How can these be measurable?
But I know every rock and tree and creature
Has a life, has a spirit, has a name
Colors of the Wind
In terms of User Interface Design, every element must serve its purpose—its reason for being. In able to be identified, it must have a name and a description of what it does.
The Name—Description—Purpose Information Structure or NDP becomes a tool in identifying any UI element within a system. The Designer would have a glimpse of what it is called (Name), what it does (Description), and why it exists (Purpose).
Be a jack of all trades and a master of none or a master of one (and more)? It is an age-old question.
It depends on the environment where you want to focus on:
In general, be the best at one thing and not so best or at least familiar with other things.
There are many default usability styles designed by the browser.
Sometimes it is best to leave it alone because it covers a lot of area that you might not be able to cover if you nitpick it.
Now if the color of the outline clashes with your branding like “blue is really banned from your UI” then change it.
Or if the outline color is the same as the background color, it won’t be seen, of course, so change it.
It’s important to note that styles whose main purpose is usability must be left alone especially if your purpose is to simply comply with color schemes.
There are initial points to take into consideration in order to make sense of the connection between HTML elements (<p>, <a>, <div>, etc.) and CSS properties (display, font-size, background-color, etc.).
You might notice that it is all about HTML elements. This is because HTML elements already have implicit CSS rules in them thru the browser. It is called the User Agent Styles or browser default styles.
Now your question borders around creating your own styles, thus, overriding the default styles.
