Posts about me and what I'm up to.
The Masaccio Exchange
Posts about the art world, theory, society, and other national topics.
Well, now that I’ve got the new version of my site up, I thought I’d take a moment for anyone interested to talk about the design decisions, theories, and methods that went into making this a reality. This new version is, I feel, a massive success in what it seeks to do, and it pushes my own online presence far beyond what I had been doing before. And while maybe all that just comes across to the viewer, it does so because of a lot of decisions I’ve fussed with over the past few weeks, the past few months, and some going back the past few years.
First up, the design was a pretty large undertaking. I’ve found out over the past five years that an artist portfolio is actually a very difficult thing to do right. Artists tend to be non-linear. Websites (and how we as people actually use them), are linear. This causes a lot of tension between artists and their websites, and how the conflict between non-linear thinking and linear display gets resolved varies a lot. I’ve seen quite a few approaches, a lot of solutions, and a lot of things that I didn’t like. I’ve seen artists try and reconcile the need for a creative, interactive space by using very free-form, experimental sites. As a designer, though, I’ve felt these have always failed the end user, serving only to satisfy the wants of the artist, and not the actual needs of the website or its users. Among other things, these creative sites tended to have one or many (if not all) of the following design shortcomings:
- A heavy reliance on Flash. While I was never of the hardline “Flash is the devil” camp, Flash was always an unwieldy solution. It was very, very programmatic to create. Very difficult to make flexible. It didn’t scale well or easily to various page heights, leading to fixed viewport style sites. It kept the data locked inside. It didn’t index into Google. It didn’t work on mobile. The list goes on…
- No permalinks. Usually because of Flash. When you went to a gallery, the address of the site didn’t change. You couldn’t bookmark or share individual pages, galleries, or images. For a portfolio page, this was absurd. It was counter-intuitive and harmful. Users are coming to look at art, and the site shouldn’t hinder them on sharing it once they have.
- Mystery-meat navigation. “Creative” sites really worked on eschewing things like labels. Unfortunately, the web lives on labels, and discarding them often meant I was clicking on anonymous images or icons, hunting around trying to guess what I’d just asked to see, and how the hell I was supposed to find what I really was trying to find. Sure, it meant the artist didn’t have to ask themselves the hard questions, like how to edit and show their work in coherent bodies, so, they felt more freed. But as an end-user, it sucked. A lot.
The sites that shy away from Flash aren’t without their own faults, though. Usually, they take the idea of “simple” to a point that’s closer to “crude.” These sites, though much preferable to the Flash ones, have a few different concerns:
- The content loads a whole page for each piece, increasing load time, interrupting the flow, and slowing down the ability to scan a body of work. Plus, it just doesn’t convey the level of polish and gloss a modern web user expects, leaving things feeling chintzy.
- The home page is often just an image, lacking any information to help orient a user. Or for Google to index.
- The layout is formulaic and static, leaving the image left to look like it’s “floating” among some scattered menu links.
- No Flash. Period.
- Permalinks are a must. Users need to be able to bookmark and share individual pieces.
- The home page needs a large key photo (since I am a visual artist, not a blogger), but also search engine-friendly text content that updates regularly.
- All sections need to be clearly labeled. All collections need to have a coherent theme, motif, or topic. Users shouldn’t have to guess any more than they have to where to find what they want.
- The images need to be as large as they can be, without requiring scrolling on smaller screens to see the entire image.
Metro UI and Gallery Aesthetics
With those goals in mind, I turned to the design mantras most concisely laid out by a rather unlikely source: Microsoft. In the original concept docs for their Metro UI used on Windows Phones, they talked about a new, modern approach to UI design that takes its cues from older, more tried design movements like Constructivism, Brutalism, and other such theories. Of particular resonance from the whitepaper on the aesthetic was the following line:
We think content should be elevated, and everything else should be minimized.
This is really the core of their philosophy, which has been fleshed out with statements like “LET’S BE HONEST. IT IS WHAT IT IS,” “TYPOGRAPHY IS BEAUTIFUL. PERIOD,” and “WHEN ALL IS SAID AND DONE, CONSUMERS WANT CONTENT.” But it keeps coming back to the simple idea of reducing and fiercely eliminating all unnecessary UI, and reducing the visual architecture (or “chrome”) that computers and the modern web have often used to deliver that content.
As a design philosophy, it’s one I’ve been working towards for a long time, and the external inspiration of the whole system has helped me define and refine that sentiment. And, it also reminds me of something else I’ve always loved: the gallery aesthetic.
Galleries tend to have a uniform look: empty walls, sparsely hung art, lots of white, very little clutter. They emphasize something that’s very important–white space. They let the art be the focus, and stay out of the way as much as they can. They strive to reduce visual distraction and cross-chatter. And they’re elegant as hell for it.
With those ideas and aesthetics in mind, I set about to looking at the last version of my site. I had to decide which elements were going to stay, and which weren’t. Then I removed everything unnecessary. The implied-page drop shadows are gone, releasing the content into more white space. Horizontal rules went too, and instead I just use comfortable, generous margins on content to provide necessary visual breaks. At the suggestion of my girlfriend, I also used an increasingly-popular web design idea known as “responsive” or “fluid” adaptive design, that lets the site fill the entire browser window. The design ration stays the same, and the experience is enarly identical for desktop resolutions from 500 to 2560 pixels wide. I moved the menu below the header images and galleries, letting the visual be the dominant cue. When text is used, it has wide margins, and large type. Only the things needed are shown at any time. The menu is sticky and joins and exits the flow as it needs to. Return to top buttons are hidden on short pages and quietly enter the picture on longer posts and pages as you scroll.
Images are given priority, and are allowed to be as large as they can be. Text takes the next visual priority, and as much as possible is done with type alone. Icons and graphics are kept to a bare minimum, with only 12 icons and graphics used across the site, and only an additional couple chrome elements (such as the shadow behind the menu and over the header) to help establish a clear visual hierarchy. All said, only 22 image files are used to make the entire site. Everything else is pure content.
The result, I feel, is gorgeous. Images are huge, and take up most of the prime visual space. The text is relevant and dynamic. Controls are pared down to just what you need, and they’re right where you expect them to be as soon as you want them. It fills the browser. It changes size as you resize your window in all browsers that properly support it.
But, it took a bit of work to make all that happen. So, for the designers among you, press on and we’ll look at some of the technical difficulties that had to be overcome and the compromises made in part 2.
I was reading over a list from UK tech site Electricpig of their favorite 100 Windows Phone apps (now that there’s a market big enough to have favorites), and lo and behold, I see a familiar icon floating around in the list. Congratulations to FourSpotProject for this, and stay tuned for what I’m hearing will be a nice update to the app soon.
Hey, look, it’s Mr. Bernhard Thielen’s excellent NewsSpot app for Google Reader featured there, with my icon work. Mmm. Feels good. Also, still an excellent app. If you’ve made the jump to what I’m convinced is the only mobile platform actually built on solid design theory, why not pick up a copy? It’s worth the coin (and, I don’t get a cut, so, this isn’t some shameless shill just to line my own pockets here, I designed the icon for Bernhard because I think his company was doing good work and wanted to support that.).
As I’m working on the new design for ZmZ here, I found the various other drafts and revisions and put together a quick and basic timeline of the site’s evolution over the past four years. I find it interesting. That is all.
Full-size huge version without the fancybox via the external link.