Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 17 Apr 2012 20:17:26 -0000
Message-ID: <20120417201726.96225.5514@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Update_of_=22Website=5FDesign=22_by_MilesFid?=
 =?utf-8?q?elman?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for c=
hange notification.

The "Website_Design" page has been changed by MilesFidelman:
http://wiki.apache.org/couchdb/Website_Design?action=3Ddiff&rev1=3D5&rev2=
=3D6

- <<Include(EditTheWiki)>>
- <<TableOfContents()>>
+ ----
+ /!\ '''Edit conflict - other version:'''
+ =

+ ----
+ <<Include(EditTheWiki)>> <<TableOfContents()>>
  =

  =3D Intro =3D
- =

  Read the [[http://s.apache.org/NsT|mailing list thread]] that spawned thi=
s page.
  =

  =3D Guidelines =3D
+ ----
+ /!\ '''Edit conflict - your version:'''
  =

+ ----
+ <<Include(EditTheWiki)>> <<TableOfContents()>>
+ =

+ =3D Guidelines =3D
+ ----
+ /!\ '''End of edit conflict'''
+ =

+ ----
  We do not vote for changes to the website design. This leads to a design =
by committee situation. And design by committee situations always produce b=
ad designs. A good design is usually the result of a unified vision. That m=
eans it is usually driven by a single individual. As such, comments and sug=
gestions should be given to that individual, and they can use it to inform =
their vision.
  =

  At the moment, we do not have a designer with that vision for our website.
@@ -20, +32 @@

  Let us know!
  =

  =3D Unreviewed Comments =3D
- =

  When adding a comment, please describe the problem. Do not describe the s=
olution. The solution is something that the person with the overall vision =
is tasked with coming up with. If you provide a solution with your problem,=
 you are confusing the matter, and limiting the scope of productive discuss=
ion.
  =

   * The main text is very large and takes up a lot of space.
- =

-    * ''Commentary: This is because the current design is set to a certain=
 width, and the main body text expands to fill that width. The size of the =
type itself is to compensate for that large width. If the type was any smal=
ler, the text would be hard to read. If we want to reduce the text size, we=
 need to reduce the width.''
+   * ''Commentary: This is because the current design is set to a certain =
width, and the main body text expands to fill that width. The size of the t=
ype itself is to compensate for that large width. If the type was any small=
er, the text would be hard to read. If we want to reduce the text size, we =
need to reduce the width.''
  =

   * The links to the mailing list web interfaces are not clear enough.
  =

   * We do not link to the Markmail web interface.
- =

-     * ''Against: These are not official, and might be better suited for t=
he wiki.''
+   * ''Against: These are not official, and might be better suited for the=
 wiki.''
+   * ''For: this is an open source project with a community - links to oth=
er sites is both common for FOSS projects and indicative of a strong user a=
nd support base - it's one of the things people look for when evaluating op=
en source software''
+   * For: searchable archives are very useful, and since the Apache mail a=
rchives don't have a search function.....
  =

   * The link to JIRA should be more prominent.
+   * ''For: Reporting bugs is a primary task for visitors to this website.=
''
  =

-    * ''For: Reporting bugs is a primary task for visitors to this website=
.''
+   * ''Against: We link to it in the footer, and this should be enough.''
  =

-    * ''Against: We link to it in the footer, and this should be enough.''
+   * ''For: the purpose of a front page is primarily navigation - make it =
easy to find things''
  =

   * The Contribute section is too long, and users might miss the Developme=
nt links under the Quick Links section.
  =

   * We should tweak the themes of JIRA and the Wiki so they better match t=
he homepage.
- =

-     * ''Commentary: JIRA probably can't be skinned, but the wiki probably=
 can be.''
+   * ''Commentary: JIRA probably can't be skinned, but the wiki probably c=
an be.''
  =

   * We should link to the documentation more prominently.
  =

   * We should have a "Support" section.
- =

-     * ''Against: I am not sure many people would be looking for this keyw=
ord.''
+   * ''Against: I am not sure many people would be looking for this keywor=
d.''
+   * ''For: fairly common button on lots of software web sites''
  =

   * The word "Contribute" is ambiguous, and "Development" might be better.
- =

-    * ''Against: "Contribute" is inclusive, "Development" is exclusive. Th=
at is the wrong framing for us.''
+   * ''Against: "Contribute" is inclusive, "Development" is exclusive. Tha=
t is the wrong framing for us.''
+   * ''For: "contribute" can be confused with monetary contributions''
  =

   * We should have a "Community" section.
  =

@@ -64, +75 @@

   * We should have links to Twitter and Facebook accounts.
  =

   * The website needs a clear demographic target.
+   * ''Commentary: Are we targeting new users, new contributors, or existi=
ng contributors? Potential new users are our biggest slice, and carry the m=
ost potential, so we should focus on those. Getting contributors is importa=
nt too, but maybe we over do it? Existing contributors probably don't need =
the website at all, and managed perfectly fine with the old one. Sorting ou=
t the answer to this question will help the solutions to other comments see=
m obvious.''
+   * ''We need to support the entire community - ranging from evaluators w=
ho have not yet decided to use CouchDB, to new users, experienced users, sy=
s admins, to developers.  The front page is primarily an entry point - it s=
hould provide navigation and links to pages tailored to more specific audie=
nces.  In particular: ''
  =

-    * ''Commentary: Are we targeting new users, new contributors, or exist=
ing contributors? Potential new users are our biggest slice, and carry the =
most potential, so we should focus on those. Getting contributors is import=
ant too, but maybe we over do it? Existing contributors probably don't need=
 the website at all, and managed perfectly fine with the old one. Sorting o=
ut the answer to this question will help the solutions to other comments se=
em obvious.''
+  . For evaluators (and I do a lot of software evaluation), the questions =
are: - what is this thing - what are the details (functionality, architectu=
re, implementation) - is the project "alive" (not in terms of a pretty site=
, but in terms of an active community of users and developers) - which impl=
ies things that change (blog, news, events, mailing lists with lots of acti=
vity, bug tracker that shows things getting fixed, ....) - who's using it -=
 details of what's involved in using it (demo, install instructions, docume=
ntation, some slideshows) - a sense of the community (blog, archives, forum=
s, links to related sites)
+ =

+  . For new users, what counts are documentation, tutorials, FAQs, an acti=
ve and friendly support community.
+ =

+  .
+ =

+  . For experienced users, updates, detailed documentation, code libraries=
 (when users are developing stuff), support for odd problems, ...
+  .
+  . For contributors it becomes a matter of technical documentation, commu=
nity, easy-to-access CVS and bugtraq, lists and community....
  =

   * The Documentation link should say Wiki
  =

@@ -76, +97 @@

   * There should be a link to the Quick Links in the header
  =

   * We should link to the Markmail interface for the mailing lists.
+   * ''Against: We already link to the official ASF interface, and that sh=
ould be enough for this site. The Markmail links can be put on the wiki.''
  =

-    * ''Against: We already link to the official ASF interface, and that s=
hould be enough for this site. The Markmail links can be put on the wiki.''
-=20