[Gimp-web] Menu proposal.

[Carol Spears]

Raphaël Quinet wrote:

>On Thu, 14 Aug 2003 18:47:32 +0200, Niklas Mattisson <scizzo@gimp.org> wrote:
>  
>
>>Hey,
>>
>>I am sorry I did forget a few things on the menu proposal:
>>
>>- News
>>- About GIMP
>>- Screenshots
>>- Downloads
>>- Tutorials
>>- Documentation
>>- GIMP Books
>>- Mailing Lists
>>- Bugzilla
>>- Getting Involved
>>- Links
>>
>>- GIMP from Source
>>- GIMP for Unix
>>- GIMP for Windows
>>- GIMP for MacOSX
>>- GIMP for OS/2
>>
>>- Contests
>>
>>This should do the trick. 
>>    
>>
>
>Yes.  But of course, I would like to change two small things:
>- Use "Bugs" instead of "Bugzilla".
>- Swap "Tutorials" and "Documentation" to have "Documentation" on top.  It
>  would be even better to remove "Tutorials" from the menu, but see below.
>  
>
The tutorials are the reason and the biggest use of the site.  You 
forget this is the users site.

Reading this makes me want to kick the documentation completely out 
of the users site and designate them only for the developers.

This is an art making app; Raphael, I am not certain how long it has 
been since you *used* TheGIMP, but this suggestion tells me that it has 
been a very very long time.

Should we completely kick anything that appears in docbook style only 
to developer.gimp.org and leave the tutorials here, so that the 
developers can figure out more easily what is going on here?

>  
>
>>I don't see the big point of moving the tutorials to the Documentation
>>because it actually has nothing at all to do with documentation.
>>    
>>
>
>Well, both of them explain how to use the GIMP.  The Documentation
>section is organized as a reference, while the Tutorials section is
>organized by themes (goal-oriented).  So the tutorials are simply a
>different way to document how to use the GIMP, and there is nothing
>wrong in having the tutorials inside the Documentation section.
>  
>
Tutorials are where artists share how they use gimp.  Tutorials are 
very special for this, imo.

Documentation is dry information presented in a predictable fashion.  
Cold.

Lets remove docbook style items from the user site totally!!

>  
>
>>[...] But
>>having the Documentation section and then add the tutorials there does
>>not make it userfriendly it turns the whole meaning of userfriendly down
>>IMHO.
>>    
>>
>
>I don't think so.  The old www.gimp.org site has the tutorials inside
>the documentation section and nobody complained about that.  On the
>contrary, I think that it makes the navigation easier by reducing the
>number of options in the menu.
>
>In fact, most of the software sites that I looked at have their
>Tutorials or HOWTOs inside a Documentation section.  That section
>usually contains a FAQ, a Manual, some Tutorials and links to Books
>(in any order).  For example:
>  GNOME (http://developer.gnome.org/doc/),
>  KDE (http://developer.kde.org/documentation/), 
>  Apache (http://httpd.apache.org/docs/),
>  GPG (http://www.gnupg.org/documentation/),
>  Python (http://www.python.org/doc/),
>  CVS (http://www.cvshome.org/docs/), ...
>
>Anyway, let's not argue forever about this: if you prefer to keep the
>tutorials in the menu, then feel free to do it.  If we get some
>feedback later saying that there are too many options in the menu
>(that would be my opinion), then we can remove the link from the menu.
>  
>
I think we prefer to remove documentation from the menu.

Also, perhaps we should discuss the name of the test site now.  These were
issues that were discussed ages ago.  I wonder who some of the blockers
to this pathetic excuse for a site are actually working for.

It is amazing to me how the blockers show up at the end with issues they
could have shared in the beginning.

Lets wait another two weeks to see if the blockers can find something else
they should have mentioned a couple of years ago.

I like the waiting.  I love to look at http://www.gimp.org and wonder and
wonder who the blockers are working for.

carol