Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F3F491E5 for ; Mon, 16 Apr 2012 17:26:27 +0000 (UTC) Received: (qmail 66055 invoked by uid 500); 16 Apr 2012 17:26:26 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 66015 invoked by uid 500); 16 Apr 2012 17:26:26 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 66006 invoked by uid 99); 16 Apr 2012 17:26:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2012 17:26:26 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com designates 209.85.215.52 as permitted sender) Received: from [209.85.215.52] (HELO mail-lpp01m010-f52.google.com) (209.85.215.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2012 17:26:22 +0000 Received: by lahi5 with SMTP id i5so5108436lah.11 for ; Mon, 16 Apr 2012 10:26:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=IDs2GYoguFQb1x3YvvHUhQN6IO4+oj92lOO2XfUSB70=; b=kM/rH/ekwQIcfqouMZCZbMAnOD05D6oJPWqgrvfQ4EAktaKKfDzYpl2ff323XZWs0o eBSMUmznGVDGzk8yOXwzdkrtP9pvbZbwuMqfYjKouUW4VcoeLWRHaoKf2jKNYgBmMQZf QSMhqpCxeZm0OABNbBRffemKquQ2AqS5KLhLVBteraI1VHXgfddIQTvPVrEjw9VF+/yY aOJocV50AoAGbctDh34IM1b2ib4u6UX/eZGsBRqfvcQ2PiO9aTnjG1JgySSCARd6ozuT HP6gg+KCaXgfqycJocJD2za78K+H0m/q2kqJ9ScUnh7TJTg058v7rD7R1RTslNldN/97 TcRA== MIME-Version: 1.0 Received: by 10.112.103.74 with SMTP id fu10mr5625788lbb.1.1334597160166; Mon, 16 Apr 2012 10:26:00 -0700 (PDT) Received: by 10.112.100.97 with HTTP; Mon, 16 Apr 2012 10:26:00 -0700 (PDT) In-Reply-To: References: <8A7F076D-84EC-433E-8160-EC5838E5FEBF@dionne-associates.com> Date: Mon, 16 Apr 2012 19:26:00 +0200 Message-ID: Subject: Re: website & jira From: Benoit Chesneau To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Apr 16, 2012 at 7:13 PM, Noah Slater wrote: > On Mon, Apr 16, 2012 at 5:04 PM, Benoit Chesneau wro= te: > >> On Sun, Apr 15, 2012 at 10:45 PM, Noah Slater >> wrote: >> > Beno=EEt: >> > >> > Please don't add anything to the top navigation. The only thing I thin= k >> we >> > should add there is a link to the "Quick Links" section - but I alread= y >> > tried that and the auto-scrolling breaks. If you can figure out a way = to >> > make it not break, please add that. >> >> Well why not about a context menu? > > > What? > http://en.wikipedia.org/wiki/Context_menu here a menu that culd appear when you click on a top navigation link. > >> > >> > Bob: >> > >> > We link to the documentation in the Quick Links footer. The documentat= ion >> > itself includes the API reference. I don't think there's any particula= r >> > need to link to the API reference on the page as a special call out. >> > >> > Beno=EEt: >> > >> > I agree that I think the text is very big, but it's the only way we co= uld >> > get it looking good with the text stretched across the whole screen. >> > Perhaps the thing to do is to shorten the width of the text some how. = We >> > need a designer to look at it. >> > >> >> Why the text has to be stretched across the whole screen? It looks >> good but it's actually really painful to read it. > > > Yes, I'm not sure what to do about it. > > We need a designer to look at it. i would first reduce the width to 40em (common width on desktop) and the font size to something human readable then look at a designer to make eventually things looking better (wich is far less important than readability). I can do that quickly if anyone is OK. > >> The links to the web interface for the mailing list are there. Click on >> the >> > mailing list names themselves. >> >> Hard time to figure I had to click on the link. That's not intuitive. >> > > Intuition is relative. Do you mean we should encourage people to try all the link before finding the right content behind? None of these links clearly tell to the user that it links to a web interface. > > >> Also I don't find the markmail link. > > > Markmail is not official. But it was there and useful. > > Not convinced this is a big deal. How many people use the web interface t= o > our mailing lists by clicking on a link, and then browsing by date? I am > willing to bet it is only me, when totting up vote. > Or any people that want to link to a discussion on others media. > >> > >> > I don't think we need JIRA in the top level nav. We have it in the Qui= ck >> > Links section. >> >> Quick link section is on the bottom. When I just want to put a ticket >> I want to make it fast. That should be on top imo and really visible >> for all. Its as important as "Download" is and probably more important >> than the mailing lists. > > > I think that the next step forward is to add a Quick Links header > navigation element that would allow you to scroll to the bottom of the > page. If anyone can get this working properly, please contribute it. > Why do i have to scroll to the bottom to find a really important link. Opening tickets is a way to encourage people to contribute. It is also the way we provide support. It really *must* be part of the top navigation. - beno=EEt