Tags filed under ‘web design’

The Comics Curmudgeon, Redesigned!

Screenshot of the new Comics Curmudgeon site design

Always an honor to get to improve upon a personal favorite!

Some of my earliest childhood memories are of reading the newspaper comics: youthful confusion about the differences between Garfield and Heathcliff, Marmaduke and Howard Huge, the Lockhorns and the Family Circus, wondering who was reading those giant-yet-boring Prince Valiant strips on Sunday, pondering the bizarre evolution of Robotman. I’ve read the comics religiously ever since, missing only a handful of days over the past 20+ years. But there were so many strips I simply ignored, convinced they were stodgy hangers-on from decades long past, or else that they were unfunny legacy soap operas not worth the time to investigate.

Thankfully in 2004 Joshua Fruhlinger started reading the comics so we wouldn’t have to. His curmudgeonly commentary had an opposite effect, though: hundreds of thousands of people suddenly began to appreciate Mary Worth for all of her meddlesome glory, found themselves able to recite the sordid back stories of the girls of Apartment 3G, and learned new ways to determine whether or not you might in fact be a Plugger.

The Comics Curmudgeon is one of the few sites that I visit multiple times a day right in the browser (despite its handy RSS feeds), so it was a great honor to be given the chance to do a facelift of the site. Since I look at it so often, I figured I’d better do a good job. Not to mention that if I broke what was already a cherished site, I’d surely be mauled by his sizable community of rabid comics fans!

Some of the highlights of the redesign:

  • An awesome new logo up there in the header depicting Josh as drawn by Ces Marciuliano, writer of Sally Forth and creator of Medium Large
  • Brand new, handcrafted WordPress theme, designed to retain some of the lo-fi, Verdana-heavy charm of the old site while cleaning up the layout and typography considerably
  • A new jQuery-based @reply system for the comments section, modeled after the ad hoc format that his community evolved and had been manually typing in — his posts often reach 500+ comments, so this helps keep track of who’s talking to whom a bit
  • A new Advanced Archives page that lets users build the archive they’d like to see (ex: “Show me this month’s posts about Mary Worth that contain the word “meddle”, in ascending order, five per page”), also allowing for easy bookmarking of their search query
  • Cleaner, lighter code and speed optimizations on the server side to help offset the time it takes to pull down the large daily comics
  • A flexible “jello” layout that expands and contracts depending on the size of your browser window, to add a bit of whitespace and breathing room without breaking things for folks on smaller screens
  • iPhone and “other” mobile versions of the site (which double as low-bandwidth alternatives for those on dialup who’d like a speed boost) with AJAX comment loading

Hopefully it’s all a change for the better (I think it is!), and I look forward to hearing the feedback!

UT Law on the Go: New iPhone Web App

Screenshots of the UT Law iPhone app

Trying to keep up with the proverbial Joneses, today we launched an iPhone / iPod Touch mobile web app for the University of Texas School of Law. If you want to check it out on your iPhone right away, fire up the following link in Safari: http://www.utexas.edu/law/m/

I built it from the ground up with PHP, JavaScript, and a bit of elbow grease, pulling data from a handful of existing sources both on-campus and off. It makes use of the iUI JavaScript framework, which is a great resource for getting up and running quickly (but which also has some drawbacks — I’ll likely switch to pure jQuery for the next major version, but I’m also keeping an eye on the jQTouch project). A quick rundown of the features of the web app:

  • Directory Search — if you’re affiliated with UT Law School you can search our internal phone and email directory by name or department, using the native iPhone apps to place calls and send emails directly,
  • Event listings and Notices pulled from our existing calendar and Law Mail announcement systems,
  • RSS feed view of our press releases,
  • Recent Twitter posts from our Communications office (this will make more sense when/if we have more than one Twitter account posting official news, and can combine them into one stream here),
  • Maps: detailed building maps, Google maps that use the iPhone location services to guide you to our building, KML-based maps of public parking, nearby hotels, and restaurants,
  • and a psuedo-iPhone style photo gallery that’s pulled from our existing mini-gallery on the regular website, adding the ability to flick through the images (did you know that Mobile Safari adds nifty JavaScript events for multi-touch gesture support? I didn’t until this project…)

There are a lot of things already in the works for the next iteration. The number one goal is to support other popular devices, to live up to the ideal of “one web, any browser”. As a developer who has wrestled against the wide range of inconsistent desktop browsers and all of their HTML and CSS inconsistencies over the years, though, it was really, really, nice to work with a single browser that already supports HTML5 and CSS3 presentation out of the box. Now I’m spoiled.

christycarroll.com

chrsitycarroll.com

The first of my summer freelance projects is now live: the portfolio site for fabulous packaging designer, Christy Carroll. Love her work! Christy crafted the visual design for the site, and I implemented it in WordPress with a completely hand-tailored jQuery portfolio browser for the homepage. More to come soon…

adamnorwood.com

adamnorwood.com 2009

Freshened up my personal blog and portfolio site for 2009. While similar to the transitional look and content that you’ve seen for the past couple of years, this theme has been hand re-written from scratch and features many advancements over the old style. The entire site is better integrated through Wordpress than ever before using features newly available in WP 2.7.1 (gravatars, per-post styles, threaded comments, etc), a handful of customized plugins, subtle jQuery enhancements, and Subversion to tie it all together on the backend. I’ve also moved to a new domain after about ten years of being at asnorwood.com. All of the old links should still point to the right place (or get you pretty close), but let me know if you find something missing.

The bulk of the improvements are behind-the-scenes, but I can at least say that the following changes make my life easier and me happier:

  • Uploading new portfolio work is much more straightforward.
    No more need for a separate gallery plugin!
  • The category and link organization is more sensible! Tags, too!
  • Better error-handling — hopefully you won’t end up 404 Not Found, but you at
    least have a sporting chance of getting unstuck now!
  • The search engine optimization (I hate that term) seems to be working
    already, too. Thanks, Google!
  • The search form pulls up better, more accurate results!

All of this tech stuff is secondary, of course, and I’m still trying to decide how best to balance the blog entries between my different interests. Maybe I’ll eventually split off into two or more distinct sites to keep things from rambling together. I’d also like to figure out a better way to incorporate the side-channel links (currently I’m using del.icio.us) and scrap-collecting elements (I love Tumblr for gathering quotes and other detritus, but not sure how best to tie that content in with my main site). Being nearly the fifteenth anniversary of my first website, you’d think I’d have this all figured out by now!

What do you think? What would you change?

Mixed Bag

mixedbag.marshariti.com

Another fairly straightforward Wordpress theme built from the ground up. This time it’s for Marsha Riti’s secondary blog, MIXED BAG, which collects her project instructions, recipes, and Craigslist finds from around Austin (are you obsessed with midcentury modern furniture and weird old junk, too?).

Hold on to your hats

adamnorwood.com launched

Hey kids! I’ve relaunched my site, moving it to its new official home at adamnorwood.com (goodbye, asnorwood.com). It’s got a new, hopefully better design, a stronger Wordpress backend (the bells and whistles have all been polished), and I’ve got a slew of new content coming down the pike (I know, the last real post on here was from…last July? Uh-oh). I’m launching it into the yawning chasm that is SXSW2009, so maybe everyone will be too distracted to notice any temporary glitches or missing bits. For you faithful who are reading this in a feed reader, I thank you and ask your forgiveness for the horribly jumbled updated feed that probably greeted you this morning!

Things to look forward to:

  • More posts on art from someone who’s trying to figure it all out, with more of a focus on the local (Austin, Texas) art scene
  • Posts on design and technology, including some lessons learned while building up my Wordpress chops
  • More signal, less noise

As always, I’d love to hear any criticisms, complaints, questions, comments, or commiserations. Leave me your good words!

Paging Dr. Sbaitso

Accessible Rich Media
Some of the best panels and meetups I attended at this year’s SXSW (the famous technology/music/film/designer eyewear festival) were on accessibility and adaptive technology, a good forum to hear what’s stirring in those fields. In particular, it seems like there’s a growing open source movement to provide tools for users with special needs and to help web designers produce accessible content.

Closed source software like JAWS will face a real challenge as open screen readers like the NVDA project become more mature and build on the popularity of other software like Firefox — while NVDA is certainly lacking the features and polish found in the more widely-used commercial products, the price (free vs. $1000) and ease-of-installation certainly make it compelling.

I also learned about the following accessibility-checking programs and Firefox extensions, immediately adding them to my developer’s toolbox:

Content Colour Analyser

  • Colour Contrast Analyser, a great tool available for Windows and OS X that gives you two color pickers: one to choose a foreground color (probably your main text color) and a second to pick a color from the background to compare it with. It then gives you detailed contrast ratio information for the two colors along with clear indicators as to whether your site or application complies with the suggested contrast needed for visually impaired users and for colorblindness. It’s one of those tools that simply works as advertised.
  • Fangs, a screen reader emulator built as a Firefox extension. When run on a page, Fangs displays a mashed-together, color-highlighted, text-only version of your content as a screen reader would read it aloud. If you’re a sighted web developer, this is a handy tool for getting a quick impression of how your page will hold up under JAWS or similar. (Bonus points for having an attractive, accessible website)
  • The Firefox Accessibility Extension from the Illinois Center for Information Technology Accessibility. This tool helps you generate reports on various accessibility issues, can display information about your page’s semantics (headings, list items, links), lets you easily switch into various high contrast modes, etc. It’s a great companion to the awesome Web Developer extension.
  • You should also check out Color Oracle, the cross-platform color blindness simulator. It’s pretty sobering if you have regular vision like I do, and it will make you appreciate that yes, two different hues can be very, very similar-looking to a good portion of your audience, and yes that’s a big problem.

(It goes without saying that these are useful but imperfect tools, never capable of giving you the full insight that would come from actual user testing. The only real way to know what real frustrations an impaired user will have with your new web app or site? Get one to come in and give it a spin!)

The other good news coming out of the past couple of weeks is the support the major browser makers are giving to the WAI-ARIA suite of standards for making web applications and forms and controls more semantic and accessible. Opera 9.5, Firefox 3, and now even IE8 (imperfectly?) are slated to support ARIA (whither Safari?). The Secrets of JavaScript Libraries panel discussion at SXSW also brought news that jQuery will soon join the Dojo toolkit in supporting ARIA-enabled widgets (I think that’s where I heard the news, feel free to correct me if I’m wrong).

These are the kinds of open source projects that I really dig: good for users, good for shaking up the established software licensing model, and good for helping solidify support for web standards. Know of any other good tools?

UT Law homepage, newly refreshed

UT Law 2008 Homepage Redux

Today sees a new homepage for the University of Texas School of Law. This iteration is more of a realign than a redesign as the decision was made to keep our interior pages intact while we continue a long-term look at our branding and online presence. The biggest design challenge was creating something cleaner and more useful for our visitors while retaining most of the same content and enough of the previous design to tie it in comfortably with our current site’s look-and-feel.

Realignment

The new version emphasizes our communication pieces, changing the rotating banner graphic into something more dynamic: the accompanying text is now HTML-based and will link to richer features similar to our Clinical Education stories. Our previous 75×75 pixel highlight buttons (which themselves were reduced from the intricate 200×140 highlight graphics of two years ago) have been folded into our general News list to help simplify the page. The navigational links were dramatically reorganized to make the hierarchy clearer and more contextual. Everything’s still there, it’s just been reshuffled.

Make it pretty

The goal aesthetically was to reduce the homepage’s clutter and to make the information presented more visually balanced. I designed the old homepage, so I’m to blame! To accommodate the larger banner graphic I increased the width of the site to 840 pixels, and then subdivided that width into a five-column layout. The typography is much more consistent, and care was taken to align the text vertically on a baseline grid. The colors are lifted from the previous version but greatly toned down — far less orange, no more crazy orange-stripe-gradient thing, and a nice white background with some subtle color at the top. Still feels like UT, but doesn’t scream it, and the new design continues to match our internal pages.

UT Law 2006 - 2008 Before and After

Behind the scenes

I’ve shifted the site from Transitional to XHTML 1.0 Strict and have made greater use of XML for the maintenance of the feature stories and news items. The layout and typography are all still handled with plain CSS: if you strip away the stylesheet, you’ll find that the homepage is semantic, streamlined, and very navigable with screenreaders or other assistive technologies. Text can be adjusted in the browser to just about any size without breaking the layout. We’re also sporting a bit of hCard markup so that folks can easily scrape our contact and location info into more useful formats.

Hopefully the refresh is just what we need to help carry us along until the sitewide redesign. I think the updated technology and cleaner look will do a lot for us, and it should help increase our visibility as one of the top-ranked law schools. If you have any comments about the design or about site refreshes, I’d love to hear them.

IE8’s Faustian Bargain

Faust IE7

“If the swift moment I entreat:
Tarry a while! You are so fair!
Then forge the shackles to my feet,
Then I will gladly perish there!
Then let them toll the passing-bell,
Then of your servitude be free,
The clock may stop, its hands fall still,
And time be over then for me!”
 — “Faust,” Norton Critical Edition, lines 1699 – 1706

The above lines are from Goethe’s story about the scholar Dr. Faust and his famous bargain. The scholar promises his soul to the devil in exchange for earthly knowledge and power, on the condition that his life will be forfeit only when he experiences a moment that he wishes would persist. What does this have to do with Internet Explorer 8? It’s a tortured and overblown metaphor to be sure, but for some reason this week’s developments in the world of web development reminded me of this fable.

If you haven’t already, start off with this article from A List Apart and perhaps move along to Eric Meyer’s analysis of the news. These articles appeared almost simultaneously with a post on the IEBlog about the scheme. To grossly summarize, the IE team has worked out a deal with some of the major players in the web standards scene and representatives of the browser makers to introduce a new <meta> tag allowing developers to target specific browser implementations. They argue that this move will help prevent complaints of new browser versions “breaking the web” when they are released to the public.

This news seems to have come as quite a surprise, with heated discussion (mostly negative as far as I can tell, and at times sadly mean-spirited) breaking out in the usual forums. Molly Holzschlag provides the most level-headed analysis I’ve read so far, and alludes to the secretive, NDA-protected discussions that led up to this decision. Even Ars Technica and El Reg have weighed in on the issue.

The contemptible part of the new specification is that it’s designed to allow sites to lock into a current implementation, and Microsoft has made the decision that the default rendering engine for pages lacking this meta tag will be IE7 (not IE8, the browser that’s introducing this feature, or the more sensible default of “latest version”!). The implications of this are that future versions of IE (and other major browsers?) will contain emulation code allowing it to switch back to a previous engine at will so that sites will always look and act the same as the designer intended, quirks and all. If you have IE10 and look at a page lacking the proper meta tag, it will use IE7 to display the page. I guess that means IE8 won’t pass the Acid2 test by default? What does that even mean?

In my humble, semi-educated opinion, this could be a major setback to the web standards movement and to the speedier development of better web technologies (and things already move at a glacial pace in the web world). We’ve been taught for years that the road to enlightenment was paved with progressive enhancement and future-proofing, and this goes against that grain. I find the idea disquieting too for its other more pragmatic implications — how will this actually be implementable? I was relieved to find in a post by Robert O’Callahan, a coder who works on Firefox, that he was puzzled by many of the same questions I was having. Won’t this increase dramatically the footprint of each successive browser release? And I’ve used emulators of all kinds in the past, and they simply aren’t perfect.

Will this end web development as we know it, or kill the open standards movement? No, of course not. But it’s confusing enough and sudden enough that it’s not surprising that more than a few people are upset by the news. Maybe I’ll warm up to it when I hear more specifics about how this will actually work in the real world, but for now I’m highly skeptical.

Update: The debate continues, with two further articles from A List Apart. The first, “They Shoot Browsers, Don’t They?” by Jeremy Keith makes the case that a good beta version of IE8 would go along way towards making the case for one side of the other, depending on how its display holds up on the current web. I’d have to agree, and I’m glad to see ALA giving a contrary opinion some space, after the articles from last month caused such an uproar. Having said that, Zeldman’s “Version Targeting: Threat or Menace?” fans the flames a bit as he tries to make his case again in favor of the default opt-in method. This time it’s revealed that major DOM scripting changes are the root cause of Microsoft’s concern, which I don’t think was mentioned previously. The argument doesn’t seem to stick, at least based on the response the article’s drawn. I still stand by my view that this is a pretty bad deal, and one that’s only intended to help Microsoft’s short-term financial interests. Check out the commentary on these two articles, though, for a handful or other good opinions. Even though there doesn’t seem to be much traction, public discourse is always welcome.

Clinical Education at UT Law

Clinical Education at UT Law

The new Clinical Education at UT Law site, showcasing the large number of community outreach programs available at the school that bring together upperclass students with real-world legal experience and service.