Posts Tagged ‘interface inventory’

We print out page designs, hand them some scissors, and get them to cut up the pages into their smallest components. Mix them all up so you can’t even tell which components came from which pages. I really like this […]

Conducting an interface inventory is a critical first step for establishing an effective interface design system. I’ve written about what interface inventories are and why they’re important, so here’s a recap of what they are: An interface inventory is similar to a content […]

The team at education startup Future Learn used atomic design as the backbone of establishing their new pattern library. I especially love how they shared why the first stab at a pattern library didn’t work: Finding specific information was often […]

Recently, the always-brilliant Scott Jehl wrote a post titled Grade components, not browsers. In his post, Scott explains that grading browser support is an ineffective way of determining what experience a particular device/browser should get. Instead, the Filament Group grades […]

Literally the same day as I introduced the concept of interface inventories, Aaron Gustafson demonstrated how to create one using Evernote. I’m pretty sure he just convinced me to take another hard look at Evernote.

Many are familiar with the concept of a content inventory. Content audits are usually performed in the early stages of a website redesign process to take stock of all a site’s content. It’s a tedious process involving spreadsheets and caffeine, […]