In class on Wednesday, I talked with my students about the importance of writing in web authoring. One of the articles they were to read, which of course they didn't (partly my fault), was Amber Simmons "Reviving Anorexic Web Writing." My students seem to believe that it is just common sense that you'd need the content of a web site before you could create or author an effective design. What they don't seem to realize is that prospective clients may not always see it this way.
Simmons tells a story of one difficult client who wanted her to drop everything and create a quick and dirty website for his latest and greatest project. Her reply . . . was to smile "at him, nodding in all the right places, and when he stopped talking for just long enough I said, 'All that sounds great. When you're ready to give me the content you want to use so I can see what I'm dealing with, let's talk. '" The clients response . . . "'Can't we just add that later, once the design is finished'" ("Reviving").
This brings up two really good points: 1) writing and design have to go hand-in-hand, and 2) it really does help if the designer is the author of the content as well. The fact is that it really does help if the designer of the web site can also be the author of the written content. If the site is intended to be somewhat playful, and you design it that way, it's likely that you can capture that essence as well in the text. An outside author may not have that ability. It's obvious that attempting to design something without content would likely equal failure.
Bottom line: never design without content, and attempt to always be the author of that content.
When I told myself that I needed to blog tonight (I mean I had already done the reading), I really did not (still do not) want to. I'm tired, it has been a rough day, and, quite frankly, the reading I did for tonight's blog left me with nothing. Not sure how I ended up with TWO readings that left me feeling nothing two nights in a row, but it has happened.
I read Dean Allen's "Reading Design" for tonight, and I highlighted all of three passages. From what I can tell, Allen is ranting about web designers lack of consideration for the reader when they choose how to represent fonts. Allen argues that the education of many of the students he teaches "had plainly focused away from what I consider the primary goal of communication design: to make vital, engaging work intended above all to be read. To use design to communicate" ("Reading Design").
The one thing that I did find useful about the article was Allen's "An Entirely Incomplete List of Things a Non-Illiterate Designer Should Know Before Being a Designer" at the very end of that article. That is worth printing and putting in a place where you'll always see it if you have plans to be or are a designer.
That is all I have to say about this article. It ain't much, but I at least I read and blogged.