On my third day in Broadcast Video Production, my teacher had a profound quote written on the blackboard. Perhaps it was not a quote, but certainly valuable wisdom. Shoot to edit was stretched across the chalky panorama, yielding any space only to the days date in the top corner. This wisdom didnt cure cancer, you didnt hear it in a love song, and it certainly didnt start a revolution, but it evoked the creative in me to start thinking not as an aspiring artist, but as an aspiring designer. Shoot to edit became design to code and build to use. Sadly, however, it seems some popular designers skipped this important lesson, and its cause a serious downfall in web technologies today.
In October of 2006, I became a member of a creative online community known as DeviantArt. I came for the Anime, and I stayed because I found the work of one Felix Valentin, my original inspiration to look for more work like his, and eventually open up Dreamweaver and Fireworks for the first time. I was a High School Freshman, and clueless as to the difference of a <head> tag and a <body> tag, but I didnt much care. I used as my canvas the still-popular MySpace website, which seemed only to grow and had no worries. Time progressed, and my work got better. Not great, but better. After a year, I hit a point where I was actually willing to post my work in my DeviantArt gallery, and as I kept learning, my work got greater and greater. It wasnt until just the start of this semester that I realized I had learned in a bizarre way that others hadnt. I knew I had taught myself, but I figured 2+2=4 regardless of how you find that out. I was wrong and I found it utterly shocking.
I figured out what it was about me that was so different: I had learned the standards together. There was no natural progression from easy to medium to hard. I started at hard and hacked away at it until I got it right. Until I could look at something and know exactly how it was done, or at least how I could do it, too. My assumption was that every site that was pumped out of Photoshop or Fireworks was created with heart and soul, and most importantly, the next stage in mind. My assumption was that every designer knew his or her way around a stylesheet and maybe even a php.ini file. My mistake. Or rather, the mistake of many designers. Thats the focus of this article: Workflow Progression and there lack of.
I want to make clear that you can have a beautiful site that is practical, but having an impractical site is virtually guarantee annoyance for you and your users. Yes, that background of a tunnel is mighty nice, but is it worth the wait to download all 2 megabytes of it? Yes, that blog looks great, but how are you going to get that type to look that good in every modern browser on every common operating system? In a design class, a student, whose section was news on the school site, pointed out to the teacher, It doesnt, like, matter if its slow. Its the only site that has the information, and they need it, so theyll just hafta wait! A week after the site that the class had created launched, the Parent, Teacher and Student Association elected an official site-checker, whose responsibility was to get information off the site and send out an e-mail newsletter so others wouldnt be forced to go to the site. Its this type of attitude that worries me. Technical feasibility is ignored in favor of shine and gloss. Accessibility is ignored in favor of making it look great on Safari.
My Call-To-Action, if you will, is this: learn. If you are a web designer, know how the web works. Dont just create something shiny in an image application and slice it up. Design knowing what kind of code youll need to use to achieve this, and how you can make it this awesome without adding 55 seconds to the load time. Know the standards, and know what kind of plugins and hacks there are for things, and dont be afraid to create something more than once or twice to find the most manageable way of doing it. If you want a blog which has titles in Gotham or Myriad Pro, learn about Cufon or SIFR. If you want an efficient way to show large photos on your homepage, dont be afraid to test a Flash component or JQuery item. My point is this: make it beautiful, but make it functional, too. Dont just create something and slice it, or outsource it to a developer who will just end up annoyed at how inefficient the design is. Think ahead, and dont be afraid to use patterns and reusable assets. And most importantly, think about the vastly different users who want to use this, but only if it enriches their lives and wont make them feel like theyre wasting their time on waiting.
--Examples-------------------
EQuilibrium Discotheque by SiostraNocyYakovae by Osec
--
Member of #designerscouch and ~ArtistUnion and *theblackpixel
seen this? [link]
Have a nice day, buddies!
--
Das ist das letzte Mal, dass ich dein Blut aufwische.
/izo\
Previous Page12345...Next Page