Responsive Web Design Challenges

The redesign process is in full swing and up until last week, it was all smooth sail­ing. Then we ran aground as we embarked upon the DESIGN por­tion of our trip. Early in the process, I threw a cur­sory glance at respon­sive web design,  assum­ing that it was some morsel of cod­ing magic that I needn’t worry about because our devel­oper would be the cap­tain of that ship. I was wrong. Not Titanic wrong, but wrong nonetheless.

While it is true that Nick is respon­si­ble for build­ing and cod­ing the site to spec, respon­sive web design required me to think very dif­fer­ently about the con­tent on the pages. So dif­fer­ently, in fact, that after 14 years of doing web work, I stopped and had a Dorothy moment. I’m not in Kansas anymore.Things can move around on the screen: text, nav­i­ga­tion, images, every­thing. It all needs to shift and com­press and breathe to fit vary­ing widths. Con­tent can and should be fluid. Where’s my compass?

So Daisy, our designer, and I took a major, unplanned side trip and delved deeply into RWD the­ory and process. Essen­tially, there are two major camps form­ing on this
topic:

  1. The RWD folks who advo­cate build­ing full-meal sites with all the con­tent and fea­tures for desk­top and then mod­ify the way the con­tent is dis­played for var­i­ous screen widths and devices via the use of media queries and CSS.
  2. The other camp claims this is a faulty approach; among them the ever-controversial Jakob Nielsen who rec­om­mends sep­a­rate mobile-optimized sites that cut fea­tures and cut content.

The real­i­ties of imple­men­ta­tion aside, I would opt for some­thing closer to Nielsen’s approach due to the fact that I am a con­tent per­son. But with­out the proper research on what our users are look­ing for on mobile plat­forms, we are choos­ing the sim­pler RWD route and will mod­ify over time or apply a hybrid ver­sion. We are a uni­ver­sity with lim­ited resources and we have to make com­pro­mises for the sake of mak­ing progress.  Our web­site needs a bail out now.

We decon­structed our process and had a healthy dis­course. We met with David Con­rad, found­ing part­ner at Design Com­mis­sion, who gave us some great guid­ance on how to approach this project.  We read many arti­cles and shared sev­eral exam­ples. We involved BJ Miller, an Infor­mat­ics stu­dent who works in IT, and he brought some good ideas to the wire­fram­ing process. We were finally all on the same page.

Some great resources:
How to Design a Mobile Respon­sive Website

Top Respon­sive Web Design Tools

Respon­sive Web Design by Ethan Marcotte

Grid­pak: The Respon­sive Grid Generator

Pod­cast from The How and Why of Respon­sive Design

Top Respon­sive Web­sites in Higher Education

Exam­ples of Good Respon­sive Design

FAQs With Style

I was recently tasked with mak­ing some improve­ments to sev­eral messy pages on the iSchool site to improve the read­abil­ity and over­all appear­ance. One of these pages was an FAQ page, one of many on the site, which was con­structed from just a bunch of text and cer­tain lines in a bold font to sug­gest that they were the ques­tions. My first thought was that this page was just a wall of text that a lot of peo­ple would just sim­ply skip over rather than try to read.

Old FAQ Page

An old FAQ page

My goal with this page was to re-design it in a way that made it seem more like a real FAQ page and become more read­able and scan­able to both a passer by and some­one look­ing for a spe­cific answer to a spe­cific ques­tion. To do this, I started off by adding some more con­trast between the ques­tions and the answers as well as adding some more space and divi­sion between the dif­fer­ent question/answer pairs. The first step here was to increase the size of each ques­tion to 18px and mak­ing the text a deep pur­ple color to con­trast the 12px black default text style of the answers. Then I added some spac­ing between each question/answer pair and throw­ing in a sub­tle light gray bor­der to clearly dis­tin­guish between dif­fer­ent ques­tions. Then, after look­ing at many exam­ples of FAQ pages on dif­fer­ent web­sites, I noticed that many sites label their ques­tions and answers with a big “Q” and “A” respec­tively. I felt that this made the site feel like even more of an FAQ page as well as adding a bit to the ease of scan­ning through the con­tent so I added these labels to the left of each ques­tion and answer, again in an 18px font.

This spe­cific FAQ page I was work­ing on had the ques­tions divided up into sev­eral sec­tions, each with their own header. The 18px font of the ques­tions, how­ever, broke the hier­ar­chy of scale with the sec­tion head­ers because they were a smaller font. A sim­ple fix for this would have been to increase the size of the sec­tion head­ers to some­thing like 24px, but after try­ing that out, It just seemed too big. I was really happy with how the ques­tions and answers were look­ing so I didn’t want to tweak the ques­tion font size at all. Instead, I came up with a dif­fer­ent approach to mak­ing the head­ers become more defined with­out going crazy with the font size. The first thing I tried was to give the head­ers a light gray back­ground to make them stand out and really divide each sec­tion. This looked alright, but with the padding of the con­tent con­tainer keep­ing the gray back­ground of the header from span­ning across the entirety of the con­tent box, I felt like it still needed some­thing to help divide the sec­tions and stand out as more promi­nent than the ques­tions. To fix this, I just took the gray box I had formed by giv­ing the header a back­ground and stretch­ing it hor­i­zon­tally so that it extended 4px past the white back­ground of the con­tent box.

New FAQ Page

The final look after all of the changes

After all of the tweaks, I was quite happy with the read­abil­ity and over­all appear­ance and so was Nick so I went ahead and applied the new styles to all of the FAQs on the site.

The one draw­back to the new style is that it involves adding a fair amount of cus­tom mark-up to the page con­tent which makes it a lit­tle tricky to do things like adding or remov­ing ques­tions and sec­tions with the WYSIWYG edi­tor. The eas­i­est way to address this issue for the time being was to just let the page own­ers know that they will have to con­tact the web team in order to do these types of changes.

With the new iSchool site cur­rently in the works, we are able to address this prob­lem in a much more ele­gant and usable way. Instead of just adding the extra markup to Page con­tent, we are work­ing on a FAQ con­tent type that uses a cus­tom field to cre­ate new ques­tions and answers and add them to an FAQ page.

FAQ Submit tool in D7

What the FAQ con­tent type might look like in the new Dru­pal 7 site.