Hard at work on a design

I don’t know about you guys, but this project has been a difficult one. I’m still trying to get the layout of my typography assignment functioning appropriately- so rather than posting a link to a finished project, I figured I’d give you a sense of how I’ve spent my time on this.

First I turned to my source material for information. As you can tell by the VERY high quality photos below, the majority of this material was collected during a research visit to church archives in Baltimore. I hoped to use these images as both typographical and compositional inspiration.

Type
Layered images of papers from Christ UMC for the Deaf archive, collected 2013.

Here I collected fonts from a number of church materials- letterheads, program books, and church registers- as well as items from the Deaf press that would be representative of this period.

Layered images of papers from Christ UMC for the Deaf archive, collected 2013.
Layered images of papers from Christ UMC for the Deaf archive, collected 2013.

I also looked at the layout and composition of these documents, collecting eight that were visually interesting.

Layered images of papers from Christ UMC for the Deaf archive, collected 2013.
Layered images of papers from Christ UMC for the Deaf archive, collected 2013.

I also began collecting some details that appeared across the texts – I’m hoping to be able to integrate these details in the final project.

Armed with some visual inspiration, I also set about developing a mock-up of the final design.

Mock-Up

You can see a rough version of it above and a link to my page here. The challenge for the past two days has been translating all the ideas into Dreamweaver.  I hope you are all having great luck with this!

This week I commented on Sara’s Blog.

Structure and Layout

The reading this week focused largely on structure and layout and it has me thinking about the page from a new perspective. Generally, I think I’ve approached print media and web pages from a functional perspective; paying more attention to content and only distracted by form when it is… distracting.

The examples in Thinking with Type,  were  great because they reinforced the importance of layout and design, from both an aesthetic and a functional standpoint. The examples on pages 152, 154, 158-159, and 188 got me thinking about how we use footnotes on a page and how this may be made more or less effective as well as more aesthetically pleasing. I connected this with last week’s reading by Dr. Petrik, Scholarship on the Web: Managing FootnotesIn the same way that the physical texts described in Lupton’s book disrupted or divulged information in meaningful ways, presenting information on the web requires thought.

HTML & CSS built on this line of thinking and forced me to consider the users of a webpage.  Who do I want to visit my webpage and what do I want them to see when they get there?

My (potential) visitors are varied. There’s the people of this class (who are forced to look at this page), my parents (who google me for no discernible reason), and, hopefully at some point, other history scholars and prospective employers.

The first two groups, I’m sorry to say, are not my focus in constructing a website. Rather, I’d like a page that fosters discussion with scholars in my field of history, primarily deaf history. And I’d like to create something that showcases my (developing) skill-set. I’m still deciding, however, what that page would look like.

This week I commented on : Beth’s and Anne’s blogs.

Typography and Design

This week focused on the subject of type, something I genuinely enjoy. I’m one of those people who harbors strong feelings about comic sans and spends a little too much time selecting fonts for projects.

Still, it was interesting to circle the topic of typography  from a number of perspectives: theoretically, practically, aesthetically, historically.  It encouraged me to think about the use of type in new in a new way.

One of the things that drew me, was the way in which people seemed both comfortable and uncomfortable describing fonts. You could simply refer to them by name, and many did, but others still searched for ways to convey the meaning of fonts. In the film Helvetica, for instance, the subjects frequently described fonts outside of spacing, cap height or ligature. Instead, they were using adjectives generally associated with objects or sensory perception, rather than type.

“this has a kind of belt and suspenders look, it needs to be, you know, much more elegant, hand-lasted shoe.” – Jonathan Hoefler

Errol Morris’s examination of this in his study of the subject, Hear, All Ye People; Hearken, O’ Earth reinforces the idea. He suggests that fonts have the capacity to evoke “truthiness”, while David Dunning suggests that a font is “slightly tuxedo.” As Jonathan Hoefler  explains in the interview,   fonts are frequently described using terms that are “qualitative… and subjective”.  They seem to evoke meaning outside of the content they represent.

As Lupton frames this concept succinctly as “typography as discourse” (Thinking with Type, pg 97). In effect, this is what Morris’s New York Times study strives to identify: if type is a form of discourse, what are it’s parameters? How does one convey “truthiness”? The film Helvetica, suggested a changing discourse – fonts took on new meaning in new contexts. Morris’ look at the history of Baskerville certainly demonstrates a changing understanding of one type face.

It made me wonder: in the future will we be judged for the vitriolic  reactions to comic sans (seen here, here, and here)?

Overall, the big points I took away from this week came with the last part of the Ducket reading in HTML & CSS . Why does this font stuff matter? Because in constructing webpages, we are choosing elements not solely based on our own personal preference. We’ve got to be aware of the interests and concerns of the potential visitors to our site. In effect, as much as I love the details of a decorative font or a script font, my readers may not. Clarity should be of heightened concern in choosing fonts.

My webpage is accessible through this blog (click on Digital Portfolio at the top of the page, or click here.)

This week I commented on: Amanda’s Blog and Becca’s Blog.

Week two:

For me, this week’s readings jumpstarted my thinking about the projects we will be generating over the course of the semester. While we’ve spent some time talking about the organization and structure of webpages in other classes, I’m looking forward to taking it a step further and testing out these ideas.

There are a lot of examples of poor web design available. (My bank has a particularly terrible webpage.)  However, identifying poor design depends on how users evaluate them. I complained about this last semester, but in celebration of a 150 year history my alma mater put together a very pretty and very ineffective timeline that showcases images and content. While it’s “pretty” and “showcases information” – it is also useless. Users can click on the highlighted events to view images or read content, but the experience ends there. There are few links to sources or lengthy descriptions and there’s no opportunity for additional interaction with historical content or other users. A redesign of the site would take into account the arguments in this week’s reading: form AND content matter. As Norman argued, an attractive and pleasant user interface improves the experience of users- but so does intelligent and careful design (Elish and Trettien).

What does it mean that people evaluate aesthetics rather than content or effectiveness in using web pages (Web Credibility)? It means we have to think carefully about how we put pages together- so that they are both pretty and useful.

This week I commented on Sara’s Blog and in my own comments below.