From docs-return-10493-apmail-httpd-docs-archive=httpd.apache.org@httpd.apache.org Tue Apr 10 16:18:52 2012 Return-Path: X-Original-To: apmail-httpd-docs-archive@www.apache.org Delivered-To: apmail-httpd-docs-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94DEB9B67 for ; Tue, 10 Apr 2012 16:18:52 +0000 (UTC) Received: (qmail 60388 invoked by uid 500); 10 Apr 2012 16:18:52 -0000 Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 60320 invoked by uid 500); 10 Apr 2012 16:18:52 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@httpd.apache.org List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 60312 invoked by uid 99); 10 Apr 2012 16:18:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2012 16:18:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.210.173] (HELO mail-iy0-f173.google.com) (209.85.210.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2012 16:18:46 +0000 Received: by iafj26 with SMTP id j26so10304768iaf.18 for ; Tue, 10 Apr 2012 09:18:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer:x-gm-message-state; bh=h49rZ1yxt6Wc9oYAJKEyTtoq9wB5Apy4+dkwztFQAaw=; b=O6mHWqOd82LtNxL3EU4t4RvYcbdSK9iRP5T/VuCsb1QUUTNCGyEh/oXkV5O8CTx3w9 nbEpFyaQGaQxTJ1c6+lOVvo5bCBsazhS/tjUPGPXRkG8TnAWDhlOywEtpAyG/Lsv+Peq eJjnztdjax7XDSKEMh5Xs+0Eldjl19oT5XHiFRBwrnmI/5rWRwrSabeDbkXhqPql9TTY SM0ZzHyJtwwEKsG0ocVYesUCZXTZq7/FufZgXHc0sfqURWSzaHOsxl1EmM6EmGNtoO7T Z5KJHs26kJ9nerMHPFZDbCz8K2lDkHRpSK3JalTOapr/BWMPIfRpnh2uSchnSlopK2pj Gfjw== Received: by 10.43.49.195 with SMTP id vb3mr7380153icb.33.1334074704821; Tue, 10 Apr 2012 09:18:24 -0700 (PDT) Received: from [192.168.200.198] (74-131-224-250.dhcp.insightbb.com. [74.131.224.250]) by mx.google.com with ESMTPS id hq3sm48420801igc.0.2012.04.10.09.18.22 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 Apr 2012 09:18:23 -0700 (PDT) From: Rich Bowen Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: multipart/alternative; boundary="Apple-Mail=_ABC222F3-A882-474E-9297-A40DA33AA9D0" Subject: Re: Docs Frontpage Date: Tue, 10 Apr 2012 12:18:21 -0400 In-Reply-To: To: docs@httpd.apache.org References: Message-Id: <4C180257-B795-439E-9839-270F9BB32D63@rcbowen.com> X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQml67yGh5299nT533+sPyR9xVugG6rIqMfbg8H2OjNEzWG60cfYYwSNq/Fr5ppbtOgzo5pf X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_ABC222F3-A882-474E-9297-A40DA33AA9D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On Apr 10, 2012, at 12:06 PM, Igor Gali=C4=87 wrote: > As I mentioned in my last mail, this: >=20 > http://httpd.apache.org/docs/current/ >=20 > is terribly uninviting for several reasons. Agreed. I'd like to see it arranged more invitingly, but my attempts to = do so haven't been very successful, possibly because I've been staring = at this arrangement for a decade and know where everything is. >=20 > The separation in several sub-sections is a good thing, > but the presentation in alphabetical order is bad. >=20 > The middle section especially should be ordered in a > way which follows a a certain progress. I wonder if we might arrange things into audiences. Casual users (eg, = folks with a web host), server admins, developers. >=20 > "Other Topics" is almost completely useless, in > particular "Other Notes", which duplicates a couple > of links, we no fresh content other than a warning > that the linked content may be outdated. Yeah, "Other" tends to mean "I don't know where to put this", and we = need to come up with an organization that eliminates that ambiguity. >=20 > I'd maybe go as far as replacing the license link with > http://www.apache.org/foundation/license-faq.html +1. > Anyway, I'd like to discuss (or maybe just decide ;) > how we can represent the existing content better. > I'm not trying to force out any howto, intro or other > stuff which some of our users might want.. We have several distinct audiences that we cater to, and they tend to = want their information in different ways. I hesitate to call them = beginner, intermediate, and advanced, but that's kind of the structure = that stuff might fit into. You mentioned possibly a "where do I start" = document, and that's actually been requested numerous times over the = years, and derailed in the discussion of what's in scope. Let's hear some other suggestions of arrangement of this content. -- Rich Bowen rbowen@rcbowen.com :: @rbowen rbowen@apache.org --Apple-Mail=_ABC222F3-A882-474E-9297-A40DA33AA9D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
As I = mentioned in my last mail, this:

 http://httpd.apache.org/doc= s/current/

is terribly uninviting for several = reasons.

Agreed. I'd like to see = it arranged more invitingly, but my attempts to do so haven't been very = successful, possibly because I've been staring at this arrangement for a = decade and know where everything is.


The = separation in several sub-sections is a good thing,
but the = presentation in alphabetical order is bad.

The middle section = especially should be ordered in a
way which follows a a certain = progress.

I wonder if we = might arrange things into audiences. Casual users (eg, folks with a web = host), server admins, developers.


"Other = Topics" is almost completely useless, in
particular "Other Notes", = which duplicates a couple
of links, we no fresh content other than a = warning
that the linked content may be = outdated.

Yeah, "Other" tends = to mean "I don't know where to put this", and we need to come up with an = organization that eliminates that = ambiguity.


I'd maybe = go as far as replacing the license link with
 http://www.apac= he.org/foundation/license-faq.html

+1.

Anyway, I'd = like to discuss (or maybe just decide ;)
how we can represent the = existing content better.
I'm not trying to force out any howto, intro = or other
stuff which some of our users might = want..

We have several distinct = audiences that we cater to, and they tend to want their information in = different ways. I hesitate to call them beginner, intermediate, and = advanced, but that's kind of the structure that stuff might fit into. = You mentioned possibly a "where do I start" document, and that's = actually been requested numerous times over the years, and derailed in = the discussion of what's in scope.

Let's hear = some other suggestions of arrangement of this content.

--
Rich Bowen
rbowen@rcbowen.com :: = @rbowen
rbowen@apache.org





= --Apple-Mail=_ABC222F3-A882-474E-9297-A40DA33AA9D0--