(Information Architecture = Cascading StyleSheets)
You can view CSS as merely a way of applying a “coat of paint” to the UI, but that misses the point, because…
Architecture and Styling are linked
… at least in our minds. Thus, our understanding and description of information are often based on
Content Integration through Context Management
Entities are not to be multiplied beyond necessity. — William of Occam
CSS (Cascading Style Sheets) is the “semantic tagging” tool by which we identify Information Architecture.
- it gives meaning to design elements
- allowing for “self awareness”, automation and sharing
IA (Information Architecture) gives weight and credibility to Cascading Stylesheets.
CSS is the “presentational styling” tool by which we engineer a CSS StyleGuide.
- it is a flexible presentation platform
- allows for easy personalization and a customized view
Cascading Style Sheets give expression and traction to Information Architecture.
UX is the infrastructure of information at the point of presentation
What factors influence a Style Guide?
- What is the intended purpose of the app/site?
- Who is the user?
- What is their agenda?
There are many more questions-to-ask, but try those 3, for starters.
‘Responsive” is a reasonable bottom-line expectation for any interactive app these days. That said,is more than just layout or UI. I believe that it can&should influence context, styling, content, and behavior. A truly responsive site is more than just Mobile.
Have, do , and focus on user-centricity. There are plenty of good tools. The right ones will emerge.
- “Mobile first’ is a popular solution that will often work, but it may not address your particular challenge.
- I love WordPress and use it myself. If your client is looking for a custom ‘heavy lifting’ workflow-driven application, it may not be the superior platform.
© The Communication Studio LLC