I’ve been thinking a lot lately about the “Responsive Design” approach, and how the problem is we’re still thinking of it as an approach, as though the alternatives are equally valid and universal. There’s “regular” design or “responsive” design.
What if we started just calling the set of techniques we’ve been calling “responsive” plain old design, and came up with an alternative label for what people used to do? (Ok, my own sites aren’t all responsive, but they will be whenever I next get around to it – the point is that new designs should all be done this way).
So I took to the twitter stream for inspiration. Storify below, enjoy.
One of the panels I proposed for SXSW Interactive 2009 was on the intersection of open source and design:
Thesis: Open Source and Design are fundamentally philosophically incompatible. Antithesis: Open Source and Design are profoundly similar in core beliefs and approaches. This talk works to articulate a meaningful synthesis between these two positions.
The talk, unfortunately, wasn’t accepted for presentation at the conference, but they suggested that instead I do a shorter, podcast or video podcast version for the Extended Content program.
In our first installment of the Extended Content series, John Eckman tells you everything you need to know about open source and design. The differences and similarities, how they benefit each other and why they have trouble getting along.
Extended Content at SXSW Interactive
(Unfortunately they don’t allow embedding, so you’ll have to go there to watch it – and at least on two browsers I tried it on, you’ll have to wait for the whole thing to preload before it starts playing – so go get a cup of coffee or whatever while it loads).
It’s just shy of 20 minutes, and having been created back in February 2009 feels (to me) a bit outdated in spots – mostly the continued evolution of the work Mark Boulton and Leisa Reichelt have been doing with the Drupal community (not just on Drupal.org but also on Drupal 7 itself), which I encourage you to check out if you’re interested in the subject.
Quick excerpt from an interview with Jeffrey Zeldman which includes some discussion of the impact of Open Source, and particularly open source CMS’s, on the process of designing and building web applications:
Although I think it’s important to draw a distinction between simple, relatively cheap licensing (the Expression Engine model) and Free and Open Source software, I generally agree that
Now, we have really powerful comparatively easy to understand, open source content management systems
And that this shift- from needing a large scale custom development project or an expensive proprietary CMS to now being able to leverage open source platforms – represents a key point in the maturity of web development.
While working on my PhD at the University of Washington, I taught for a couple of years in an Interdisciplinary Writing Program. The fundamental concept of the IWP was to address a fundamental problem common to first and second year composition classes, which is the lack of context.
(A brief aside on “writing in the disciplines” or “interdisciplinary writing” programs: Most college composition courses take one of two approaches: the either ask the students to write about literature or they take a topical approach, choosing topics in which they believe the students will be interested. The former approach assumes the students are interested in what the instructor is interested in, as many of these courses are taught by graduate students or professors whose real interest is something literary. The latter creates an environment in which the ostensible topic of the writing is an artificial academic context usually dealt with very superficially, since the real purpose of the course is the writing, not the topic. IWP and programs like it try to solve that by situating the students and the instructor in a real academic context: an existing undergraduate course in another discipline. The students’ writing tasks are situated in an authentic environment, where they are actually trying to understand and enter an ongoing academic discourse.)
(Sorry for the mms links – you can rip them via mplayer if you need to watch in offline mode, but I think reposting them here would be considered a copyright violation).
Both really celebrate / argue for what we might call the situatedness of technology design: the ways in which an understanding of the cultural context of technology use needs to be brought back into the design of those technologies and how non-engineering approaches (from the social sciences in danah’s talk and from Design in Buxton’s talk) can help to provide that context.