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!
You know what happens in Week 1, right? Yes, planning. In other words, nothing… yet. All on pencil and paper.
The action begins in Week 2. Now, here are some of the things that are new to me:
Designers must establish a typographic hierarchy in their web designs.
This is not random; this is written in a style sheet; this is designed.
The typographic hierarchy aids in making reading web texts easier.
When posting in Status format, you may only post in the content area and leave the title blank.
In case you do not want the WordPress generated ID of the post, you may choose to have a ISO 8601 Timestamp.
Edit the slug of your post and paste the timestamp.
CSS Objects are selectors.
CSS Buckets are rules.
Prioritize defining objects over defining rules.
[codepen_embed height=”265″ theme_id=”dark” slug_hash=”LjjVWE” default_tab=”css” user=”BrianSahagun”]See the Pen CSS Jot Down 1: Prioritize Objects by Brian Dys Sahagun (@BrianSahagun) on CodePen.[/codepen_embed]
The purpose is to make each object independent.
Use CSS variables for shared styles when possible.
Someday soon, there will be a CSS function that would apply a rule to a selector.
Combine objects:
Prioritize objects:
HTML could accommodate Intentions Oriented Programming (IOP).
IOP is based on intentions rather than constructs.
Code could be validated but a deeper level and meaning depends on the intentions of the programmer.
In designing the user interface (UI) of an app, it is common to start with the design of the populated state of the UI. As designers, we envision perfect scenarios, common flows, and predictable results. This, understandably, contains the bulk of work a designer has to face. It contains all sorts of issues that need to be addressed.
In turn, we might neglect designing for the different states of the component or the whole system that we are designing.
In general, here are the different states a component might be in:
