Alexei Fedotov wrote:
Talking about standard conventions, I suggest being close to
http://httpd.apache.org/. Any other candidates?

I don't get what we're doing here.

The objection to our menu was that it was "long". The httpd site is "long".

So why not suggestion specific fixes for our site (if "long" isn't a problem) that solve users needs rather than just switch wholesale to a different site that was targeted at a completely different audience?

geir



On 12/11/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:


Alexei Fedotov wrote:
> I like the design proposed by Nadya because it is compact. That is why
> the design is much friendlier for a newcomer. Gurus such as Salikh
> could maintain their own bookmarks for in-depth places of interest.
>

The thing to realize is that the original menu was one based on much
experience over many sites, with a lot of the standard conventions
expected by people generally familiar with open source sites.

> I'm ok with removing a source code page since a prefferred way to get
> code for all except technical writers is a federated build.
>
>
> On 12/11/06, Morozova, Nadezhda <[EMAIL PROTECTED]> wrote:
>> Hi,
>> More responses below.
>>
>> >(-) Renaming "Contribution policy" -> "Contributing" makes the link
>> vague
>> +1, but do you think we can say just "Policy"? the page is about several
>> notions.
>> >(-) Removing subcomponents map from the navigation pane (I use it all
>> the
>> >time)
>> +1 agreed to do earlier. Won't keep the classlib status page though -
>> have a more current wiki instead.
>> >(-) Removing "Source code" link (I use it regularly). And downloads
>> page is
>> >not
>> >the place I would go to look for a source code repository information.
>> +1 ok, I see it's a tension point.
>> >(-) Renaming "Mailing lists" -> "Subscribe" ("subscribe" is less
>> >informative)
>> -1 disagree. I tried to make this group of links more visitor-oriented,
>> add simple typical action verbs. It seems more important than the
>> abstract "lists" group.
>> >(-) The section "In the project" has no clearly defined subject and
>> looks
>> >like
>> >a heap of links randomly collected together.
>> 0. hesitant. I don't know - I've tried to group the links for those
>> already in the project. The problem with some pages there - they're not
>> as good as they should be. Suggestions welcome.
>> >(-) Moving "Downloads" from "General" section to "Get involved"
>> section.
>> >Most
>> >of our users are not going to be involved. They would just want to
>> download
>> >and
>> >use the JDK/JRE.
>> 0. reluctant. I'd prefer to keep General focused on the project, on
>> people and policy and goals. And I am not sure we have too many users
>> who want the JDK and won't be involved at all :)
>> >(-) Renaming navigation subsection "Community" -> "Get involved". It
>> now
>> >duplicates with the page title, and does not provide a logical
>> explanation
>> >of
>> >what links are listed in the section. "Community" was explaining the
>> group
>> >of
>> >links better.
>> 0. hesitant. Community is more like people inside, and get involved is
>> more like resources for people outside. Just my opinion.
>> >(+) "JIRA" -> "Submit a bug" ("JIRA" is way too cryptic)
>> >(+) removing "ASF" link
>>  :)
>> >(*) FAQ page looks outdated and needs to be revised (e.g. in response
>> to
>> >Sun
>> >open-sourcing hotspot etc.)
>> +1 will file a JIRA..
>> >(*) "Site map" link in the navigation pane deserves a subsection of its
>> >own,
>> >and need not be grouped with any other links.
>> +1
>>
>> Cheers,
>> Nadya
>>
>>
>> >-----Original Message-----
>> >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Salikh Zakirov
>> >Sent: Monday, December 11, 2006 8:46 PM
>> >To: dev@harmony.apache.org
>> >Subject: Re: [doc][user experience] minor improvements to website
>> >navigation and content
>> >
>> >Morozova, Nadezhda wrote:
>> >> Hi all,
>> >>
>> >>
>> >>
>> >> I've experimented a bit with our website to improve browsing and make
>> >> key pages or ideas stand out more.
>> >>
>> >> See http://people.apache.org/~nadinem/docs/
>> >
>> >Sorry, my first response may have been overly emotional.
>> >Here is the detailed list of issues I noticed:
>> >
>> >I think the following changes are not good:
>> >(-) Renaming "Contribution policy" -> "Contributing" makes the link
>> vague
>> >(-) Removing subcomponents map from the navigation pane (I use it all
>> the
>> >time)
>> >(-) Removing "Source code" link (I use it regularly). And downloads
>> page is
>> >not
>> >the place I would go to look for a source code repository information.
>> >(-) Renaming "Mailing lists" -> "Subscribe" ("subscribe" is less
>> >informative)
>> >(-) The section "In the project" has no clearly defined subject and
>> looks
>> >like
>> >a heap of links randomly collected together.
>> >(-) Moving "Downloads" from "General" section to "Get involved"
>> section.
>> >Most
>> >of our users are not going to be involved. They would just want to
>> download
>> >and
>> >use the JDK/JRE.
>> >(-) Renaming navigation subsection "Community" -> "Get involved". It
>> now
>> >duplicates with the page title, and does not provide a logical
>> explanation
>> >of
>> >what links are listed in the section. "Community" was explaining the
>> group
>> >of
>> >links better.
>> >
>> >
>> >The following changes look good to me:
>> >(+) "JIRA" -> "Submit a bug" ("JIRA" is way too cryptic)
>> >(+) removing "ASF" link
>> >
>> >The following items need further attention
>> >(*) FAQ page looks outdated and needs to be revised (e.g. in response
>> to
>> >Sun
>> >open-sourcing hotspot etc.)
>> >(*) "Submit an issue" does not lead to a link submission form, but to a
>> >issue
>> >browser. IMHO, it should be renamed to "issue tracker" or "bug
>> tracker".
>> >(*) "Site map" link in the navigation pane deserves a subsection of its
>> >own,
>> >and need not be grouped with any other links.
>>
>
>



Reply via email to