Creativecommons.org Development - Revision history

Alex at 22:58, 15 December 2008

2008-12-15T22:58:46Z

Alex at 22:53, 15 December 2008

2008-12-15T22:53:09Z

Michelle Thorne: /* Near duplicate content */ added duplicate page

2008-10-21T09:50:57Z

‎Near duplicate content: added duplicate page

Eric Steuer: /* Site Architecture and Design */

2008-10-08T15:10:16Z

‎Site Architecture and Design

Eric Steuer: /* Theme and Layout */

2008-10-08T15:08:12Z

‎Theme and Layout

Eric Steuer: /* Wiki Main Page */

2008-10-08T14:59:15Z

‎Wiki Main Page

Eric Steuer: /* /about */

2008-10-08T14:41:44Z

‎/about

Eric Steuer: /* Information and Content */

2008-10-08T14:39:29Z

‎Information and Content

Eric Steuer: /* Site Architecture and Design */

2008-10-08T14:28:44Z

‎Site Architecture and Design

CCID-diane peters: /* License Chooser */

2008-10-08T11:32:31Z

‎License Chooser

@@ Line 112: / Line 112: @@
 *** More information presented in less space without feeling cluttered.
 *** Visually divide posts into columns based on tag/categories (i.e. music, education, etc.)
-*** See [http://worldchanging.org/http://worldchanging.org/ worldchanging.org]
+*** See [http://worldchanging.org/ worldchanging.org]
 * Expand scope to include not only stories that directly reference CC, but also ones on related topics.
 ** "Zoom out" on issues on to put news pieces into context.

@@ Line 8: / Line 8: @@
 * I agree with Kinkade for the most part, but I think that the blog serves a secondary purpose of showing people who come to the site that there is always interesting news happening in our world and that there are always cool projects that we are working on. So, while I agree that the blog should not be the focus of the page (I mean, right now, the site looks like little more than a blog when you land on the front page), I think the fact that the blog is newsy and provides dynamic content is a major plus, and that it should remain in some form on the front page. I kind of like how the EFF handles updates on their site (http://www.eff.org/), although I'm not crazy about their overall design. (ES)
 ** The licenses are our 'bread and butter' - they should be featured here in some form (perhaps just the conditions) in a way that is straight forward and simple (Cameron Parkins)
-* The "Support" tab has an unfortunate name.  When I'm at a website and I see a link to "Support" the first thing I think about is "Technical Support" or Help, not a place where I can donate money or buy things.  It could perhaps be made more clear with something like "Support CC" or "Donate" or anything that disambiguates it from the normal "help me" meaning on the web. (Nathan Kinkade)
+* <strike>The "Support" tab has an unfortunate name.  When I'm at a website and I see a link to "Support" the first thing I think about is "Technical Support" or Help, not a place where I can donate money or buy things.  It could perhaps be made more clear with something like "Support CC" or "Donate" or anything that disambiguates it from the normal "help me" meaning on the web. (Nathan Kinkade) </strike>
 * Agree with Kinkade. I like the site menu http://www.greenpeace.org/usa/ (on the left), both for its design and language. (ES)
-* The "Participate" tab should be renamed to something like "Wiki" or "CC Wiki" so that it's clear that CC has a wiki.  My mind makes no natural connection between the word "participate" and a wiki.  People, even non-technical ones, know about wikis these days, and to make it clearer on the front page that we have one might increase the traffic to it. (Nathan Kinkade)
+* <strike>The "Participate" tab should be renamed to something like "Wiki" or "CC Wiki" so that it's clear that CC has a wiki.  My mind makes no natural connection between the word "participate" and a wiki.  People, even non-technical ones, know about wikis these days, and to make it clearer on the front page that we have one might increase the traffic to it. (Nathan Kinkade)</strike>
 * Suggestion to make front page 'stupidly simple'
 ** Two LARGE (150x150px) green buttons on dark background
@@ Line 23: / Line 23: @@
 * I think the landing main page should have minimal content, but to explain in a concise compelling way why CC is important, what we offer, etc.. (MR)
 * I agree that the blog should not be the landing page (MR)
-* I think that the support button should be either Join or Take Action - and should be a different color than the rest. I know *take action* sounds cheesy, but it does cause people to click through.(MR)
+* <strike>I think that the support button should be either Join or Take Action - and should be a different color than the rest. I know *take action* sounds cheesy, but it does cause people to click through.(MR)</strike>
-* Need a quick way to sign-up for the newsletter and events, as of right now both are extremely buried. Both of these options are great methods of community building and outreach and we should be promoting them as much as possible(MR)
+* <strike>Need a quick way to sign-up for the newsletter and events, as of right now both are extremely buried. Both of these options are great methods of community building and outreach and we should be promoting them as much as possible(MR)</strike>
 = Information and Content =
@@ Line 47: / Line 47: @@
 * I agree with this in essence, which is why I usually push for us to describe CC as either "a nonprofit that promotes the sharing and reuse of creative works" or "works to increase the amount of creative material available to the public for free and legal use" rather than "provides copyright licenses/legal tools, etc." Most people's eyes glaze over when you mention "copyright" and they've nearly passed out with boredom by the time you get to the word "licenses." (ES)
-* The About page starts with "Creative Commons is a Massachusetts-chartered 501(c)(3) tax-exempt charitable corporation." Not very helpful. I'd like to see this page totally rewritten. (ES)
+* <strike>The About page starts with "Creative Commons is a Massachusetts-chartered 501(c)(3) tax-exempt charitable corporation." Not very helpful. I'd like to see this page totally rewritten. (ES)</strike>
@@ Line 78: / Line 78: @@
 === /about ===
-* The About page is currently a compendium of links to many things that having nothing to do with CC as an organization.  To me, the About page should have nothing more than a synopsis of the organization, the history and perhaps a link to the People/Staff page. (Nathan Kinkade)
+* Section revised on 12/11/2008 - AR
 * I mostly agree w/ Kinkade, although I think some of the links on this page do have a place there (videos, for instance). (ES)
-* The licensing links should be taken off About and instead have a link to license info on the main page. (MR)
+* <strike>The About page is currently a compendium of links to many things that having nothing to do with CC as an organization.  To me, the About page should have nothing more than a synopsis of the organization, the history and perhaps a link to the People/Staff page. (Nathan Kinkade)</strike>
 === /contact ===

@@ Line 67: / Line 67: @@
 ** http://creativecommons.org/about/licenses/meet-the-licenses
 ** http://wiki.creativecommons.org/License_Examples
 === Wiki Main Page ===

@@ Line 6: / Line 6: @@
 * How can I use/understand CC easily and efficiently?
 * '''Remove the blog from the front page of the site''' and replace it with a concise summary of CC and a handful of highly relevant links to other parts of the site.  I seriously doubt whether many people go to CC.org simply to read the blog, and those that do will have no problem clicking on a new tab that says "Weblog."  Most people interested in the CC blog are probably somewhat technical and will most likely be using a feed aggregator of some sort.  Rename "Jurisdiction News" to something like "Latest News" and incorporate items from the CC blog into the list, then move the list into the right column where there is presently nothing but whitespace, thereby leaving more room for relevant content in the main content area. (Nathan Kinkade)
-* I agree with Kinkade for the most part, but I think that the blog serves a secondary purpose of showing people who come to the site that there is always interesting news happening in our world and that there are always cool projects that we are working on. So, while I agree that the blog should not be the focus of the page (I mean, right now, the site looks like little more than a blog when you land on the front page), I think the fact that the blog is newsy and provides dynamic content is a major plus, and that it should remain in some form on the front page. I kind of like how the EFF handles updates on their site (http://www.eff.org/), although I'm not crazy about their overall design. (Eric Steuer)
+* I agree with Kinkade for the most part, but I think that the blog serves a secondary purpose of showing people who come to the site that there is always interesting news happening in our world and that there are always cool projects that we are working on. So, while I agree that the blog should not be the focus of the page (I mean, right now, the site looks like little more than a blog when you land on the front page), I think the fact that the blog is newsy and provides dynamic content is a major plus, and that it should remain in some form on the front page. I kind of like how the EFF handles updates on their site (http://www.eff.org/), although I'm not crazy about their overall design. (ES)
 ** The licenses are our 'bread and butter' - they should be featured here in some form (perhaps just the conditions) in a way that is straight forward and simple (Cameron Parkins)
 * The "Support" tab has an unfortunate name.  When I'm at a website and I see a link to "Support" the first thing I think about is "Technical Support" or Help, not a place where I can donate money or buy things.  It could perhaps be made more clear with something like "Support CC" or "Donate" or anything that disambiguates it from the normal "help me" meaning on the web. (Nathan Kinkade)
-* Totally agree with Kinkade. (Eric Steuer)
+* Agree with Kinkade. I like the site menu http://www.greenpeace.org/usa/ (on the left), both for its design and language. (ES)
 * The "Participate" tab should be renamed to something like "Wiki" or "CC Wiki" so that it's clear that CC has a wiki.  My mind makes no natural connection between the word "participate" and a wiki.  People, even non-technical ones, know about wikis these days, and to make it clearer on the front page that we have one might increase the traffic to it. (Nathan Kinkade)
 * Suggestion to make front page 'stupidly simple'

@@ Line 88: / Line 88: @@
 * New design ideas Alex has been working on look very fresh to me - having them placed through out the site would be a nice way to liven up the look
 ** This will also keep CC's web properties in aesthetic coherence (Cameron Parkins)
 = License Chooser =

@@ Line 72: / Line 72: @@
 * http://wiki.creativecommons.org/Main_Page -- way too much text and way too much info to take in; could definitely be streamlined so that pertinent info is easy to find right away. Good idea to have the "Participate" tab changed to "CC Wiki," and though many people visiting the site may know what a wiki is, not everyone will - so it would be worth it to briefly explain what the wiki is and does, and how an individual can navigate and use it. (AD)
 * To much explanatory text about the links on the main page. Should just link to the pages and have relevant info there. (MR)
 === /about ===

@@ Line 30: / Line 30: @@
 * Overview
 ** An average, non-technical, person should be able to come to CC.ORG, and very quickly find out the basics of what CC provides and how it can help him. As it stands, a first time visitor has a hard time digging into the dense information currently provided.
-** (Not sure who wrote the above, but this is Eric): This really is the thing. You have to get pretty far into the site before you can really figure out wtf is going on. For sheer simplicity, I do like Google.org's (http://www.google.org/) information design.
+** (Not sure who wrote the above, but this is Eric): This really is the thing. You have to get pretty far into the site before you can really figure out what is going on. For sheer simplicity, I do like Google.org's (http://www.google.org/) information design.
 * Ideally, less words up front.
@@ Line 46: / Line 46: @@
 * I think sometimes we focus so much on what we provide, we lose sight of what we enable people to do. The latter is the more humanistic component of CC and the side that more people will relate to/understand. (MR)
 * I agree with this in essence, which is why I usually push for us to describe CC as either "a nonprofit that promotes the sharing and reuse of creative works" or "works to increase the amount of creative material available to the public for free and legal use" rather than "provides copyright licenses/legal tools, etc." Most people's eyes glaze over when you mention "copyright" and they've nearly passed out with boredom by the time you get to the word "licenses." (ES)
 == Specific pages needing overhaul ==

@@ Line 87: / Line 87: @@
 * Updated results page
 * There is a fairly urgent need to reword the descriptive text to clarify unambiguously and in no uncertain terms that the chooser is in no way whatsoever a registration form, nor is it creating a unique license of any sort.  It's need to explicitly state, and probably in a highlighted fashion, that it is nothing more and nothing less than a helpful tool to help someone select the right type of license, and also useful for generating some good HTML for the purposes of marking a work online.  I can't tell you how many info@ emails I get where people think that they are creating a license or registering a work.  And if the info@ emails can be taken a somewhat representative sample of the general CC-using public, then there is a huge amount of mis-understanding floating around. (Nathan Kinkade)
 = Deeds =