
đź‘‹ Oi, mga repapips, Brian Dys here! I love music, photography, and creative stuff like UX design and art. This is a place where I collect my thoughts and works. Apart all these, I’m Jaycelle’s better half and Bryce’s dad. 🥰
I still could not wrap my head around the whole idea of frames. However, I did like the structure that was described in relation to linguistics.
We could notice the structure—from the detail towards the bigger picture. Patterns like these are also relevant to Information Architecture.
There could be two approaches in defining elements in a User Interface (UI):
Say, for example, we have a blog post that has a date. In order to define what kind of date it is, we could either define it in a sentence:
or we could define it thru a label:
Please note that in order to create an effective description that communicates its purpose, we have to identify the context in which the element is in.
To empower designers in working in the Interaction Design stage.
The arrangement of the parts to make sense of the whole.
The language that we use and the meaning that we intend.
Where to look for Nouns?
Parts of a Controlled Vocabulary
In order to begin organizing, use facets:
These are the common taxonomic patterns:
5 Ways to Organize things:
In finding the best term for separating a collection of items, which to use—list or group?
Brain dump:
List implies linearity, structure.
Group implies randomness.
—
In generalizing the semantics of all items in a collection—in an HTML document—go for group.
<ul class="list group">…</ul> <div class="group">…</div> <dl class="list group">…</dl>
—
It is important to note that the all HTML elements in the examples could express hierarchy by nesting other elements—but it is in the collection of items that list or group provides semantics.
To recap:
Use list for collection of items that implies order (yes, even for <ul>).
Use group for collection of items that does not imply order.
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).