Content Developer Gets A Nip and Tuck.
The beginning of a new month feels like an appropriate time to spend a moment talking about the new look here at ContentDeveloper.com.
Over the last few weeks Content Developer has moved from the 700 pixel wide two column look it started out with 18 months ago, to a brief stop last week on a 800 pixel wide 3 column design, to the now 940 pixel wide 4 column design where I think we will stay for a while.
The main reason for the brief stop at the 3 column design was my own personal difficulty in kicking the 800X600 screen resolution user to the curb. Well, kicking to the curb may be a little hyperbolic since the 800X600 user can still access Content Developer just fine, but now they have to scroll a bit left to right to see everything.
Many developers and designers are also apparently still struggling with this 800X600 question.
Choosing the highest value adding minimum user spec to serve as your design baseline has always been an important first step for many online projects. Developers thankfully were able to toss the 640X480 user overboard many moons ago and for the longest time all the projects I’d been associated with usually settled in at 800X600 as the generally accepted bottom rung of the user ladder. That’s a comfortable position to defend and continues to make some sense seeing as how even Windows XP Professional x64 still defaults to Super VGA on a fresh install.
So 800X600 is still in the game, but after reviewing some recent data and implementing 4 column designs that seem to flourish with that little bit of extra space on some other sites, I’m finally starting to lean toward adopting the 1024X768 user as the new default minimum spec.
Every project has its own decision process to go through, but should 1024X768 be the new default minimum design spec for browser based projects? And if you do make that leap are you committing that all too common error of putting the interests of designers and developers over the interests of the user?
According to W3Counter.com 800X600 resolution users now account for about 10-11% of internet users.
This is just one source and though their sample size is large it probably isn’t a truly scientific representative sample. Other sources (1, 2) show that it might be a bit low but do suggest that the figure is at least in the ballpark.
That 10%-20% range of 800X600 users is still plenty big enough for a site delivering mainstream content to a wide audience to care about and pay attention to. If I’m building a general audience site designed to deliver information about health care, then I am building with that 800X600 user still very much in mind. But what pushed me over the edge for this site was an acceptance (rationalization?) that the typical reader of blogs about creating content and media distribution is probably not running on that 800X600 minimum spec.
There is an argument to be made that the use of percentages in your CSS design is the answer to this challenge. You can create attractive, clean and functional designs built around allocating your screen real estate with ratios, but sometimes the use of percantages create new viewing inconsistency issues and impose their own limitations on what you can ultimately do.
So despite some still lingering cognitive dissonance I decided to stick with a fixed width design but say goodbye to 800X600. You’ve been a reliable friend 800X600 and we will likely meet again on other projects, but your time may have finally passed for this site.
A couple other additions to the new version of Content Developer I also wanted to mention are the freshened up masthead and the introduction of headlines from other blogs and traditional news sites about content.
These headlines are delivered via that great rss feed splicing and redistribution combo of feedblendr and feed2js. Feed2js now has moved off of its longtime home on the maricopa.edu servers and onto their own site provided by Modevia Web Services at feed2js.org. The announcement on the movement of feed2js also notes that an open source feed2js site will be coming to sourceforge soon.
A couple other indicators worth noting from the W3Counter stats is the still rising market share power of Firefox…
…and the steady 3% market share of Mac users.
Has that Mac market share number changed at all in the last 10 years? Even after all those great commercials?
I hope you find that the new look here works well for you.
|
Content Developer on Twitter
contentdevelopr: Liked "The Revenge Of Editorials": Archived podcast from @SXSW Interactive about content curation and craftsmanship. www.sxsw.com/node/4864Tweet sent 10:04 AM on 05/24/2010. contentdevelopr: Reading: Using the YouTube APIs to Build Monetizable Applications - http://tinyurl.com/monetize-youtube-api
Tweet sent 10:35 AM on 03/29/2010. contentdevelopr: Some good advice: “Start creating meaningful and compelling content that can be found, shared, evangelized and measured.” http://is.gd/8ak56
Tweet sent 09:23 AM on 02/22/2010. contentdevelopr: HTML5 vs. Flash: Reporters’ Roundtable Podcast w/ @rafe @stshank and @jwherrman - http://is.gd/8wYLE
Tweet sent 09:33 AM on 02/17/2010. contentdevelopr: Like the new @TWiT netcast “Home Theater Geeks” http://twit.tv/htg - Video version also available at http://odtv.me
Tweet sent 06:07 PM on 01/05/2010. contentdevelopr: RT @onlyopensource Information Week: GPL Vs. FSF ... http://bit.ly/Izznh
Tweet sent 10:15 AM on 09/25/2009. contentdevelopr: RT @cmswire Living on the Edge of Global Web Content Management Crisis http://bit.ly/QA4Hx
Tweet sent 09:55 AM on 09/11/2009. contentdevelopr: If you’re wondering what a video ad inserted into a print page looks like, @AdAgeVideo has a peek. http://is.gd/2wsj9
Tweet sent 09:47 AM on 08/24/2009. follow content developer on twitter...