The past 12 months have been marked by a rising interest for responsive web design techniques in higher education.
Last year at the #heweb11 conference in Austin the focus was on mobile. While Brett Pollack (UCSD) and Nathan Gerber (UVU) mentioned RWD in their presentations, RWD was still perceived as a small part of the solution.
Looking at the schedules of the top 2012 web conferences in higher education (including the upcoming heweb12 in Milwaukee in a few days), it is clear that RWD has now moved front and center.
I’ve written a bit about the topic on this blog and elsewhere, but I’ve limited my coverage to homepage implementations of the responsive web design approach, mainly for 2 reasons:
- Many institutions chose to roll RWD on their homepages first
- Nobody usually bothers to make a big announcement when second-level pages are redesigned (that’s also why I’m asking for your help at the bottom of this post :-)
Lately, I’ve been getting questions on the best way to tackle the “responsive challenge” beyond the homepage.
In the virtual reunion Stewart Foss, the instructor of our 4-week online course on responsive web design for higher ed, led for his students last month, he presented, among other things, one of these “content” pages, a project Tatjana Salcedo (UVM) completed in only 4 weeks as part of the course. Here’s a 1-minute video excerpt of what he said about it.
Many other good examples of content pages can be found on the University of Nebraska-Lincoln (UNL) website.
As Seth Meranda will explain in his presentation on the topic at the High Ed Web conference (Oct 9), the UNL Web Developer Network rolled out last March a site-wide initiative to go responsive at the institutional level. They provided resources and templates to all the people managing UNL websites and got 500,000 pages redesigned AND responsive in a record time!
What’s really surprising is the fact that UNL homepage was still NOT responsive at the time of this writing as you can see below.
Seth Meranda confirmed that the RWD homepage should finally be released by the end of this week. UPDATE Oct 3, 2012: it’s now live!
How about that as a different way of doing things, UNL?
Seth explained in a Twitter direct message that it happened for several reasons (“front page needed re-architecture, lessons to be learned from lower-level pages, priorities, and others”). He also told me that while he would have prefered to do the homepage first, it has not been an issue thanks to a mobile version of the homepage acting as a proxy where all mobile traffic gets redirected.
Implementing a “responsive” approach beyond the homepage definitely requires some thinking, planning as well as a good command of the different RWD techniques This is why many of our RWD course students choose to work on this kind of pages with the help and guidance of our instructor.
Yet, I’m sure that several institutions have rolled out this approach to their content pages as well. I would love to feature more examples in a future post.
So, if YOU have – or know an institution that has – achieved RWD bliss (well, gone responsive beyond the homepage that is), would you do me a big favor and post a link to one of these RWD content pages?
I will compile a list from which we can all benefit from. Thanks for your help!
4-week online course: Mobile & Responsive Web Design for Higher Ed
(asynchronous with weekly lessons and assignments)
ONLY 10 seats per session