- We design and build extraordinary applications for companies looking to make the next great idea a reality.
- learn more
A New Workflow for Web Designers
It was Tim Berners Lee's original vision of the web that online documents be both readable and writable. He notes in his book "Weaving the Web" that that he was disappointed with the way the browser was initially developed as a read only technology, making it expensive and onerous for the asses to publish online content, and essentially creating a top down system, with lots and lots of readers but few writers.
Only recently has the technology that allows anyone to easily publish and edit online documents, in the form of Wiki's and Blogs, been developed. These tools have become so popular, so ubiquitous precisely because they cater to what users really want, fulfilling the potential that the web's founding father had envisioned for it almost 20 years ago.
And so given users obvious preferences for updated relevant content on the web, the ability to provide feedback to the wider community and the technology to allow web sites to provide all of this, I suppose that it's only a matter of time before all web sites are blogs or wikis, and the three terms become synonymous. The blogging and Wiki tools available today provide enough functionality and flexibility, are easy enough to implement, and give site owners so much advantage over traditional, mostly static web sites, that I don't see why any web solution couldn't or shouldn't be delivered as a Blog or Wiki.
Web design/development tools such as Adobe Dreamweaver, with their powerful but complex tools, and their steep learning curves, are designed to work with the traditional notion of the browser as a dumb viewport. As wikis and blogs--as well as the open source web based CMS's (such as Drupal, Joomla and even Wordpress)-- become the default method for creating, editing and viewing web pages, and hence as the browser comes to house more and more of the web publishing workflow, tools such as Dreamweaver will lose much of their value unless they evolve to support this new paradigm. The notion that a web site is like a painting, or sculpture, or some other piece of static art is outdated. Expensive tools that cater to this notion, by making it easy to waste hours manipulating the 'canvas' pixel by pixel are becoming unnecessary or even counter-productive. More so than ever, the web is a changing environment. It's easier, and better web design practice to get something online quickly, and tweak, or manage your design as it grows. Tools that support this new way of doing things are browser based and mostly free. There is still a lot of room for them to grow, especially in terms of usability, but I don't see traditional web design tools being able to compete without adapting to this new landscape.
Eventually, as the web becomes more of a democracy, and the viewing-publishing dichotomy breaks down, web designers will have to make more of an effort to work with these new rules, and the software that has enabled the web to flourish from a visual standpoint up until now will have to adapt as well.
Topics: CMS, Web Design, workflow
Comments: 2 so far
Leave a comment
About Pathfinder
Recent
- Firefox Plugin Malware ‘Trojan.PWS.ChromeInject.A’
- Pathfinder releases version 1 of the its Flash Platform microsite (codename Mica)
- Pimp my Rails: Five Plugins & Gems to Make Rails Better
- iPhone: Using Pre-processor Directives for Device Testing
- Subtle OpenGL Projection Matrix Difference Between iPhone Simulator and Device
- App Security: Throw Out the Org Chart!
- Pimp my jQuery: Five plugins to replace the features Prototype and Scriptaculous users expect
- Thanksgiving 2008: What We’re Thankful For (In Rails)
- iPhone SDK: Testing with TextMate & GTM
- GWTQuery - JQuery-like Syntax in GWT
Archives
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006


Haven’t finished reading your article, but I think you mean “masses”, not “asses” in the first paragraph. Although “assess” does give it nice humorous touch.
Comment by T.J., Wednesday, July 2, 2008 @ 10:13 am
The point that desktop tools will need to adapt to a growing web-as-software-platform paradigm, is one easy to agree with. Though I’d say that that democratization of web production and content publication cuts both ways: generally diminishing quality, while allowing the “asses” (masses
their say.
For “It’s easier, and better web design practice to get something online quickly, and tweak, or manage your design as it grows.” This, for me, is just lack of experience: ignorance of the interdependencies between elements (purpose, use, visual design, interaction design, IA/content organization, etc. etc.). Best web design practice is to plan what you build, so to design for expansion. Otherwise a wild weed grows organically and loses the sense clarity and organization necessary for trust, which is indispensable to good communication. This for the same reason you build nothing else this way: not a house, shed, or even bird house. Plan, design, produce, evaluate. Rinse and repeat.
Comment by uxdesign.com, Saturday, July 5, 2008 @ 11:21 am