couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "Website_Design" by NoahSlater
Date Mon, 16 Apr 2012 22:57:25 GMT
Dear Wiki user,

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

The "Website_Design" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Website_Design

New page:
<<Include(EditTheWiki)>>
<<TableOfContents()>>

= Guidelines =

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 bad designs. A good design is usually the
result of a unified vision. That means it is usually driven by a single individual. As such,
comments and suggestions 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.

We are actively looking for one.

Does this sound like you?

Let us know!

= Unreviewed Comments =

When adding a comment, please describe the problem. Do not describe the solution. 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 discussion.

 * 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 smaller, 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 the wiki.''

 * The link to JIRA should be more prominent.

   * ''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.''

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

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

    * ''Commentary: JIRA probably can't be skinned, but the wiki probably can 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 keyword.''

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

   * ''Against: "Contribute" is inclusive, "Development" is exclusive. That is the wrong framing
for us.''

 * We should have a "Community" section.

 * We should have a "Events" section.

 * We should have a "Demo" section.

 * 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 existing contributors?
Potential new users are our biggest slice, and carry the most potential, so we should focus
on those. Getting contributors is important 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
out the answer to this question will help the solutions to other comments seem obvious.''

Mime
View raw message